home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
BBS Toolkit
/
BBS Toolkit.iso
/
qbbs
/
xfd_v301.zip
/
XFDDOCEN.DOC
< prev
Wrap
Text File
|
1992-05-31
|
247KB
|
4,793 lines
╔══════════════════════════════ ┌─────────────────┐
║ XFD FileDoor for QBBS, SBBS │ D.I.S.P. │────┐
║ and RA alike system │ │░░░░│
╟────────────────────────────── │ │░░░░│
║ (c) 1991 Robert W.van Hoeven │ Dutch │░░░░│
╟────────────────────────────── │ Independent │░░░░│
║ Release : 3.01 │ ShareWare │░░░░│
║ Rel.Date: 01th June 1992 │ Programmer│░░░░│
╠══════════════════════════════ └─────────────────┘░░░░│
║ | │░░░░░░░░░░░░░░░░░│
║ | └─────────────────┘
║ | ┌─────┐ |
║ | │░░░░░│ |
║ | └──┬──┘ |
║ Use the XFD.NEW file for a | ┌────┴────┐ |
║ reference of new options !!! ------││││││ ═══│-------
║ └─────────┘
╠═══════════════════════════════
║ Address: Robert W. van Hoeven
║ PO. Box 131
║ 1170 AC Badhoevedorp
║ Nederland / Holland
╚═══════════════════════════════
┌───────┬─────────────────────────────────────────────────────────────┐
│ 0 │ Table of contents │
└───────┴─────────────────────────────────────────────────────────────┘
1 ---- General information
1.1 Copyrights and License Agreement
1.2 Newer versions and contacting the author
2 ---- Package description and requirements
2.1 Preface
2.2 Requirements
2.3 Included files
2.4 History
2.5 Introduction & specs
3 ---- Installation description
3.1 Installation (general)
3.2 Installation in the BBS
3.2.1 Command-line options
3.2.2 Downloads
3.2.3 Uploads
3.3 FILEDOOR.CFG
3.3.1 The line-tags
3.3.2 Very special statements
3.3.3 Basic statements
3.3.4 Statements that define the environment that FILEDOOR uses
(paths)
3.3.5 Statements that define the logging-format
3.3.6 Other statements, not related to protocol definition
3.3.7 Filedoor's Protocol Definition
3.4 FD_UPD and FILEDOOR.UPD
4 ---- Runtime information
4.1 Fast Modems
4.2 Multi-line operations
4.3 Swapping
4.4 FileDoor/DISP-compatible tag-file <tm>
4.5 File selection
4.6 Selection with wildcards
4.7 Sysop-to-User files
4.8 Local keyboard codes
4.9 FILES.CTL and BADFILES.CTL
4.10 FileDoor and conversion exits (MTA.EXE and others)
5 ---- Version information and credits
5.1 The BETA-team
5.2 Credits
5.3 Version history
5.4 Copyright, Trademarks
┌───────┬─────────────────────────────────────────────────────────────┐
│ 1 │ General information │
└───────┴─────────────────────────────────────────────────────────────┘
1.1 Copyrights and License Agreement
────────────────────────────────────
- When we refer to the XFD- and OFD-package, we mean the program
called FileDoor <tm> and all related documentation, support files
and such, as combined in the release package;
- Users of the XFD-package must accept this disclaimer of warranty:
- The XFD-package is supplied as is. The author disclaims
all warranties, expressed or implied, including, without limitation,
the warranties of merchantability and of fitness for any purpose.
The author assumes no liability for damages, direct or
consequential, which may result from the use of the XFD-package;
- The XFD-package is a "shareware program" and is provided at no
charge to the user for evaluation. Feel free to share it with your
friends, but please do not give it away altered or as part of
another system. The essence of "user-supported" software is to
provide personal computer users with quality software without high
prices, and yet to provide incentive for programmers to continue to
develop new products.
- If you find this program useful and find that you are using and
continue the use of the XFD-package after a 30 days trial period,
you must register the XFD-package as described below;
- Non-commercial users can get a license for the usage up to this
release of the XFD-package by sending a postcard, stating their
name, address, country, FIDO-address (if any) and the release they
are using, to the author (Robert W. van Hoeven) on the address
mentioned in the header of this documentation. So called 'closed
BBS's', unless they are for commercial usage, are seen as
non-commercial users;
- For commercial usage, the user must contact Robert W. van Hoeven (see
address in the header) for details;
- The registration of the XFD-package will license ONE copy for use on
any computer at any one time, as long as the usage confirms to the
type of registration you have done (so NON-commercial usage when you
have a non-commercial license);
- Anyone distributing the XFD-package for any kind of remuneration
must first contact the Author at the address above for
authorization.
- You are encouraged to pass a copy of the XFD-package along to
your friends for evaluation. Please encourage them to register
their copy if they find that they can use it;
- Support on XFD, when used in a non-commercial environment, is
available by means of written letters or by entering the inter-
national echomail area DISP;
- Problems and suggestions can be entered in the FidoNet <tm> Echomail
conference <tm> called DISP (international). Entering this echo does
not exclude you of the duty to register the XFD-package, though
users who evaluate the product can enter the echo for questions;
- The XFD-package, all programs, the documentation and support-files
is copyrighted 1990,92 by Robert W. van Hoeven, PO. Box 131,
Badhoevedorp 1170AC, Holland. All rights are reserved. You may copy
this package for backup purposes. Also you may copy and share
unmodified copies of the whole package, providing that the copyright
notice is reproduced and included on all copies.
Excluded from this statement are the support-files written by other
authors. Please refer to the documentation of these programs for
copyrights and license agreements;
- It is forbidden to modify, adapt, translate, reverse engineer,
decompile and/or disassemble the software in the XFD-package.
Patching the medium at places that carry the software is seen as a
program change and is also forbidden. It is forbidden to create a so
called 'bypass' to skip the original introduction screens and delay.
Also it is forbidden to use such a 'bypass' unless supplied by the
author (Robert W. van Hoeven) himself;
- Performing any of the illegal actions as stated in the previous
lines, is a theft and no fair play to the author and, more
important, to the registered users;
- Bulletin Board Systems that distribute the XFD package can convert
the WHOLE package to any archive-system they like but all original
files must be included in the new archive. The XFD-package on the
Bulletin Board can contain at the most 2 extra files. These files
can only be a commercial for that Bulletin Board and/or validation
data that is presented as a service to all users and shall have no
other functions;
- After the normal trial period of 30 days, you must register the
soft- ware (see REGISTER.XFD) or you must remove it from your PC;
- Comments, suggestions and bug reports are welcome and will be
answered as soon I have the time to do so. You can send me a letter
of leave a NetMail <tm> message named to Rob Van.hoeven (mind the
point) on node 2:512/100 (RA Support, Monster, Holland, SysOp is
Reinier de Groot). When you want to send me normal mail, address it
to: Robert W. van Hoeven, PO. Box 131, 1171 AC Badhoevedorp,
Holland; Also you can enter messages in the FidoNet <tm> DISP
Echomail <tm> area;
1.2 Newer versions and contacting the author
───────────────────────────────────────────────────────────────────────
The newest version of XFD is always available at the DISP-HQ on node
2:512/100. XFD is also distributed thru a number of DISP support
nodes. There are three ways of obtaining newer versions of XFD:
- Logging on at DISP-HQ or a support node
Look into the file SUPPORT.XFD for a full list of support nodes;
- Logging on to a SDS node
XFD is distributed thru SDS/SDN, but only big minors (x.10, x.20 and
so on) and majors (14.01, 15.01 and so on) are submitted to the SDS
distribution point in Holland;
- Logging on to your own BBS;
Chances are, that you will find an older version (international
users) because it will take some time for the new version to 'bleed'
thru the net;
If you think you have found problems in XFD, or in any other case, you
wish to contact the author, you can send me:
- A letter to the address you can find in the header of this file;
- A NetMail <tm> message to Rob Van.hoeven (please mind the point
between Van and Hoeven) at 2:512/100 or (better) 2:512/100.5;
- A Message in the FidoNet <tm> DISP echomail <tm> area;
┌───────┬─────────────────────────────────────────────────────────────┐
│ 2 │ Package description and requirements │
└───────┴─────────────────────────────────────────────────────────────┘
2.1 Preface
───────────────────────────────────────────────────────────────────────
Please notice the following:
- FileDoor is a ShareWare product in every right way, this means this
software is not crippled in any way. Also FileDoor is FREE ! Only a
postcard and some stamps are needed to register FileDoor. It is very
strange to see other products call themselves 'FileDoor compatible'
or 'FileDoor clone' while they ask money for the program (and some
of the ideas from others);
- Everyone is urged to register the program when using it for a period
longer than 30 days;
- This program will need the actual protocol drivers to work. These
are not supplied in this package, but are widely available on most
BBS's. Therefor please contact the author of the protocol driver
when you have problems with the driver. You may contact the author
of FileDoor or one of the support boards when you have a question on
how to install a certain file-transfer protocol in FileDoor. Also, a
large number of users can help you with the installation of certain
protocols. Refer to the RA_UTIL international echomail. Some
protocols include the settings for FileDoor, but be sure that these
are the correct ones and are compatible with the current release of
FileDoor. At the moment there is one author that has access to the
latest FileDoor beta releases to develop his protocol. This is the
author of the protocol called Zyrion <tm>;
- If you have created a working example in FileDoor.CFG for a new type
of protocol, I would like it very much if you send me a copy of the
actual PROTOCOL-statement. With newer releases, other can benefit
from this knowledge. Your name will be added to the 'what's new'
list at the bottom;
2.2 Requirements
───────────────────────────────────────────────────────────────────────
FileDoor - PC XT/AT/386;
- At least 300K free memory for FileDoor to run.
Some extra kBs are added for each file you select.
Extra memory requirements are depending on the
selected protocol driver;
- DOS 3.xx and higher (tested with DOS 5.xx and 4Dos
4.0);
- A BBS program like Remote Access <tm>, QuickBBS
<tm>, SBBS <tm> or one that is compatible with
one of the above BBS programs;
- Optionally, MTA <tm> and MTS <tm> DISP products;
2.3 Included files
───────────────────────────────────────────────────────────────────────
The package includes : FILEDOOR.EXE The main program
FILE_OVR.EXE The main program overlay version
FILE_OVR.OVR The overlay file for FILE_OVR.EXE
FILEDOOR.CFG An example config file
FILEDOOR.MUL An example config file
BIMODEM.CFG An example of Bimodem.CFG
XFD.NEW What is new in current version
XFDDOCEN.DOC The documentation
REGISTER.XFD Registration information
REG_FORM.XFD Registration form
VENDOR.XFD Vendor information
README.XFD Last minute information
*.ANS Example of ANSI -menu/Help files
*.ASC Example of ASCII-menu/Help files
2.4 History
───────────────────────────────────────────────────────────────────────
FileDoor <tm> is an original product from Stig Jacobsen. His program
was a widely used protocol driver on many BBS's in all zones and nets.
The last version (v1.21) was released in 1989 and since then
implemented in many QuickBBS and Remote Access BBS systems (the last
be means of some tricks to fool Remote Access and FileDoor).
All rights of FileDoor and the complete source code were transferred
to me in the late 1990's. Because of his work and many other
activities Stig was not able to release a much wanted updated version
for the currently supported BBS systems and the newer ones.
In the beginning I started to work with the original source code. For
several reasons this method was abandoned and I decided to write a
completely new version from scratch. This way I could use all the
experience with Turbo Pascal (my second native language) and all
available commercial toolboxes.
To accommodate the user with the fastest performance that is possible
in Pascal (Pascal implementations are always use somewhat more memory
and are somewhat slower than C implementations) a number of registered
commercial toolboxes are used to gain in speed and to reduce the
memory. A complete list of the used products is found at the end of
the document.
The current version of FileDoor is a complete rewrite and extends
file-transfer options of many BBS programs. The tradeoff is a bigger
memory consumption. There are several options in FileDoor 3.xx that
were not available before and all these options will cost some memory.
I saw no problems in extending the memory usage because most BBS
programs now have a swap-option in their external calls (like the type
7 *M option) and for those BBS's that don't have these options,
FileDoor itself can also swap before a protocol is called. It should
also be noticed that all ORIGINAL functions of FileDoor still are (and
will stay) in the program. The benefit is, that you can easy upgrade
to a newer version, the tradeoff is that the basic point of few can
not be altered.
The current version you own will work for QuickBBS, Remote Access,
SuperBBS and compatible clones. A separate package will be available
soon (OFD_Vxxx) that will interface to OPUS, Maximus and compatible
clones. BBS programs that have a newer beta-version will (sometimes)
not work if the internal structures are changed. There is only direct
access to Remote Access's <tm> beta versions and most of the time,
FileDoor will be able to work with the newer beta versions of this
program.
A special word for the current FileDoor 2.xx <tm> users. The current
version (3.01) has taken some time. It has been tested over and over
to remove as much of the bugs in 2.03 as possible. Also there are many
new features, in fact the number of NEW features is around as much as
the total number of features in 2.03. The next release(s) will take
less time. Please take a look into chapter 2.6 to see some previews
of the features I am working on right now !
2.5 Introduction & specs
───────────────────────────────────────────────────────────────────────
FileDoor is an interface to hook external file-transfer programs into
Remote Access, QuickBBS and SBBS or compatible clones of these
systems.
FileDoor will add features and flexibility to transferring files,
which will not be found in any BBS or file-transfer interface.
FileDoor has:
- an interface to Remote Access, QuickBBS and SuperBBS systems. Remote
Access 0.xx and 1.xx are both supported as are the QuickBBS 2.xx
and SBBS 1.1x types;
- full security support, including security levels and flags of the
above mentioned BBS programs;
- support for the FILES.RA/FLSEARCH.CTL file;
- support for FILES.CTL and BADFILES.CTL;
- full multi-node, multitasking capabilities;
- support for many (255) external file-transfer protocols, including
those producing a DSZLog alike LOG file;
- Built-in Fossil support;
- support for Bidirectional transfer protocols (Bimodem and HSLink);
- support for CD-ROM systems when implemented in the BBS;
- File-counter ([xx]) support;
- user ratio monitoring;
- direct updating in the BBS, if supported by the BBS;
- support for external help and menu files;
- ultra fast AutoSearch and in-archive file-view options;
- an option to refuse 'unwanted' files. (*.GIF, ARJ230.EXE etc);
- configurable download hours;
- extended and user friendly interface to select files for transfer;
- macro support;
- several exit points for third party products;
- a direct interface for semi-auto-download with the FileDoor/DISP
compatible tag-file options;
- Retaining the same easy interface for (the much forgotten) ASCII
user group;
- all those options not found in most BBS program or any other
transfer interface;
- Interfaces to MTA, MTS and other DISP products;
2.6 Thoughts on FileDoor
───────────────────────────────────────────────────────────────────────
I would like a moment of your time to share with you the ideas I have
about FileDoor and doors in general.
When I took over FileDoor from Stig I still found it the most useful
door ever written for QBBS/SBBS/RA BBS systems. It was easy to work
with, worked almost perfect and was rather fast. The deal I made with
Stig was that I should not alter the basic idea of the program. I knew
that in advance and agreed on this ! The FileDoor you see before you
has still the same functional skeleton as the older 1.21 (Stig's last
version). Some new functions are build AROUND this skeleton but do not
replace it.
My general idea of doors is much the same as you see in FileDoor. I
think that a door should be designed to complement a BBS's internal
feature or replace it with something much better. What I try not to do
is to think for the user. In my opinion it is much better to have 4
doors, each complementing each other, with each bringing the best
there is, than to have 1 general door that can do everything. Unless
very well written, those doors will not give you the best of ALL the
functions or are better in some and lesser in other. Also, such doors
can better be converted to a BBS program itself because they force you
only to use the BBS program as a skeleton and not as a BBS. If this is
the case in your implementation, you should allow yourself to recon-
sider if you run the right BBS program for your taste. Given this
(personal) idea, I make doors that can complement each other (like
FileDoor, MTS and RFW) but still leave you free to replace one or more
with a door that is more to your taste (eg. replace RFW with something
else and still getting the best from MTS and FileDoor). The main goal
is to leave the choice to you and not to the program.
Given this info, I don't have any problems with 'compatible' doors and
certainly not when they fit more into your own BBS-environment. If
there is a GENERAL demand for specific new features, they will be
implemented in FileDoor. If I find something of interest myself, I
also will consider to implement it. So the future of FileDoor is up
to you.
Version 3.01 will bring a lot of new features that will be NEW at the
moment of release (clones will duplicate them soon). There are also
a lot of features NOT implemented. These are on the list for the next
release (which by the way WON'T take as long as this release). One of
the main features is language support ! If you are interested in a
multi-language transfer door at this moment and it is a feature which
you can't do without, switch to another product ASAP, I don't mind. I
want to have happy customers (even for the price of US $ 0,-- !!!) !
┌───────┬─────────────────────────────────────────────────────────────┐
│ 3 │ Installation description │
└───────┴─────────────────────────────────────────────────────────────┘
3.1 Installation of files
───────────────────────────────────────────────────────────────────────
Installing FileDoor is quite simple assuming you have read the DOC
file. First read the part on how to install FileDoor.Exe in your BBS
system, then carefully read the part about the configuration file
(FILEDOOR.CFG). When you take the time to read every possible option
while creating the control-file you will see that everything is not
that difficult at all and you can get the most out of FileDoor.
Installation can be done as follows:
- Place FILEDOOR.EXE and FILEDOOR.CFG in some directory in the DOS
PATH. For the time being, do the same with FILEUSER.EXE and
FILEMAIN.EXE;
- You must decide if you want to use the normal version (which will
take around 350K by itself and extending the memory constraint if
you use many features) or the overlayed version (in which case you
will have a reduction of around 100K with the disadvantage of some
loss in speed). If you use the overlayed version, you should do the
following:
- Replace FILEDOOR.EXE by FILE_OVR.EXE and FILE_OVR.OVR. You can
rename FILE_OVR.EXE to FILEDOOR.EXE provided that you ALSO rename
FILE_OVR.OVR to FILEDOOR.OVR;
- You can set the environment variable XFDOVRSZ to some value. It
will be used by the overlay version to determine the size of the
overlay buffer in conventional memory. The default value (which is
around 32K) will give enough speed but you can extend the value
(SET XFDOVRSZ=50000 or another value) to gain some speed;
- The overlay version will load the overlay-file into EMS if EMS is
available and there is enough EMS-memory free. If you have don't
want to use EMS for the overlay, you can set the environment
variable XFDOVROE to N (SET XFDOVROE=N);
- Edit the FILEDOOR.CFG file in this directory (see instructions). It
is possible to use one FILEDOOR.CFx file for each line you run but
you can also create ONE FILEDOOR.CFG for all lines (see later);
- Take special care with memory requirements (see later);
- Be sure to set DSZLOG to a valid directory and filename (for each
line a separate file or separate directory). Read 4.2 in case of
doubt;
FileDoor.CFG can be found in the following ways:
- -C[drive:][\path\][filename] on the type 7/15 menu command-line;
- In the current directory, the directory FileDoor.EXE was executed
from or the DOS PATH (in that order);
- From an environment variable FILEDOOR:
SET FILEDOOR=[drive][\path\] to show the directory where
FileDoor.CFG is located
(don't forget the trailing
backslash)
SET FILEDOOR=[drive][\path\][filename] to show path and file to use
as configuration file;
3.2 Installation in the BBS
───────────────────────────────────────────────────────────────────────
The program is installed as a type 7 (shell to file) or type 15 (exit
to DOS) in your Remote Access/QuickBBS/SuperBBS menu. Although a type
7 exit is faster and much easier to install, it will use more memory.
So depending on your hardware you must either choose for a type 7 or a
type 15 exit. Both the DORINFOx.DEF and EXITINFO.BBS file are needed
by FileDoor. Depending on your hardware limitations you may also use
the swap-to-memory or disk option of your specific BBS program.
Some general hints while implementing FileDoor <tm> into a BBS:
- Either use one download menu for each file-area you have or use the
same download menu in all areas when you install the AutoSearch
option into FileDoor.CFG (advised). With AutoSearch enabled,
FileDoor will track the security to determine from which areas the
user can or may not download;
- Use at least one upload (-DU) menu for each file-area. The upload
menus can point to the same or different upload directories;
- Never allow uploads to be available for download at once. This can
cause a 'flow' of illegal (commercial) software on your BBS and any
infected file (viri) can be downloaded at once. It will only give
YOU (and not the uploader which in most cases will be a fake-user)
troubles;
- Previous releases of FileDoor <tm> (2.01, 2.02(a) and 2.03) had an
option for bi-directional protocols. This option is removed and the
bi-directional protocols can now reside in the download AND upload
menus (-DD and -DU). In either case, the user is free to choose if
she/he wants to download and/or upload, independent from the type of
menu (-DD or -DU) but ONLY for bi-directional protocols;
- When possible, use the memory swapping option of your BBS (*M). It
will cause the BBS to swap from memory, leaving more room for
FileDoor <tm> and its options of which most will be put on the
dynamic (conventional) memory (heap). Also inside FileDoor <tm> you
have the option to swap the FileDoor out of memory before the
protocol is fetched, leaving more memory for huge memory consumptive
protocols (like Bimodem);
The installation inside the BBS program is simple. The only thing you
have to take care of, are the correct switches (command-line options)
and the specific menu-syntax for your own BBS program.
3.2 Command-line switches
───────────────────────────────────────────────────────────────────────
FileDoor <tm> can use the following command-line switches of which
some are optional and some are mandatory:
┌─────────────────────────────────────────────────────────────────────┐
│ -DD │
│ -DU │
└─────────────────────────────────────────────────────────────────────┘
Function: One of these two switches (but only one) MUST be present.
Use -DD in the call to FileDoor <tm> that is used for the
download and use -DU in the call that is used for upload.
The old -DB option (do Bimodem) is removed from FileDoor and
should be replaced by either -DD or -DU;
┌─────────────────────────────────────────────────────────────────────┐
│ -A[directory] │
└─────────────────────────────────────────────────────────────────────┘
Function: This option is only needed when you do NOT set the option
AutoSearch in FileDoor.CFG. If this case [directory] will
point to the directory from which files are downloaded.
This is only needed when you have separate FileDoor menus
for separate file-areas (not recommended). When you use the
AutoSearch option in FileDoor.CFG you can leave out the -A
command-line option (or it will be ignored);
┌─────────────────────────────────────────────────────────────────────┐
│ -U[directory] │
└─────────────────────────────────────────────────────────────────────┘
Function: This option is only needed when you force FileDoor <tm> into
upload-mode (-DU) or you use one or more bi-directional
protocols (Bimodem <tm>, HSLink <tm>) in download-mode. The
command-line option must point to the directory in which the
uploads will be placed (normal non-private uploads). If the
FileDoor <tm> program does not need the option but it is
still present on the command-line, it will ignore the
option. If you include the upload-directory as an option in
the CFG-file, you can leave out the -U.
┌─────────────────────────────────────────────────────────────────────┐
│ -P[directory] │
└─────────────────────────────────────────────────────────────────────┘
Function: This option is only needed when you force FileDoor <tm> into
upload-mode (-DU) or you use one or more bi-directional
protocols (Bimodem <tm>, HSLink <tm>) in download-mode AND
you allow PRIVATE uploads. The command-line option must
point to the directory in which the PRIVATE uploads will be
placed (not the normal uploads). uploads will be placed
(normal non-private uploads). If the FileDoor <tm> program
does not need the option but it is still present on the
command-line, it will ignore the option. If you include the
private upload-directory as an option in the CFG-file, you
can leave out the -P.
┌─────────────────────────────────────────────────────────────────────┐
│ -N[line] │
└─────────────────────────────────────────────────────────────────────┘
Function: When you have a BBS with multiple lines, you must set this
command-line option to the line on which this FileDoor <tm>
is running. Most QBBS/RA/SBBS alike BBS's have a macro in
the menu-type 7 which will be substituted by the actual
line-number (*N in most cases). Some Remote Access <tm>
versions don't allow the usage of this macro more than once
(so -N*N -CFILEDOOR.CF*N for line 1 will be substituted by
RA into -N1 -CFILEDOOR.CF*N, as you see the second *N is not
replaced by '1'). In this case it is advised that you DON'T
use the -N command-line option but the BBSLine option in
FileDoor.CFG. In this case, you create a FileDoor.CFG of
each line (FileDoor.CF1, FileDoor.CF2 and so on) and you use
the -CFILEDOOR.CF*N (without -N*N) to point to the correct
CFG-file. Inside this CFG-files you have placed the BBSLine
option.
If you use only one CFG-file for several lines (using the
special syntax described later), you MUST use the -N
command-line option !
┌─────────────────────────────────────────────────────────────────────┐
│ -C[path] │
└─────────────────────────────────────────────────────────────────────┘
Function: With this command-line option, you can point to an alternate
CFG-file. This comes in handy with multi-line setups. You
can use the special BBS-macro's to point to various lines
(e.g. -CC:\FILEDOOR\FILEDOOR.CF*N) or to an alternate CFG to
make a difference between normal modems and locked (HST and
such) modems. You can use the combination of -N and -C or
one of the both and in combination with FileDoor's special
syntax for the CFG-file to gain the optimal result (see the
examples FILEDOOR.CFG and FILEDOOR.MUL in the distribution
archive).
┌─────────────────────────────────────────────────────────────────────┐
│ -F[path] │
└─────────────────────────────────────────────────────────────────────┘
Function: You can use FileDoor <tm> to force the download of a single
(pre-assigned) file like the ALLFILES.xxx file. In this case
you must create a separate menu where you use the -F option
to point to the drive, directory and name of the file in
question (e.g. -FC:\MYFILES\ALLFILES.ZIP). If you do not
include the -X command-line option, the user will come into
the menu where she/he can select the protocol. After this
selection, the transfer can be started at once and there is
no option select other files. The -F is even enhanced. You
can also include a file-mask (with wildcards) so multiple
files can be downloaded in one run;
┌─────────────────────────────────────────────────────────────────────┐
│ -X[protocol-letter] │
└─────────────────────────────────────────────────────────────────────┘
Function: This command-line option can be used in combination with the
-F command-line option (but also stand-alone). It can be
used to pre-determine the type of protocol to use. Though
useless in most cases, it IS possible to pre-determine the
type of protocol from the SysOp's point of view. When
available, [protocol-letter] must be the letter of one of
the protocols that you implemented in FileDoor <tm>. The
user will NOT have the option to select a protocol of
her/his own !
┌─────────────────────────────────────────────────────────────────────┐
│ -L[path] │
└─────────────────────────────────────────────────────────────────────┘
Function: This command-line option can be used to set (overrule) the
place and name of the FileDoor <tm> log-file. Normally you
will set the location and name of the log-file with an
option in FileDoor.CFG but you can use this command-line
option to overrule the value you set in the FileDoor.CFG.
Some BBS programs have a macro in the menu-interface which
will be substituted with the full path to the BBS-log. In
these cases the -L command-line option comes in handy.
3.2.2 Download
───────────────────────────────────────────────────────────────────────
When installing FILEDOOR.EXE for downloads in Remote Access,
QuickBBS or SuperBBS as a type 7 exit, the optional datafield should
at least contain the following:
[Drive:\Path\]FILEDOOR.EXE -DD -A[directory] {swap-macro}
The -A switch may be omitted when you have the AutoSearch feature
enabled.
FileDoor will use all BBS program specific files like FILES.RA in
Remote Access environment to do security locking. As mentioned before
you may also use the switch to swap your BBS program for a large part
to EMS/Disk ({swap-macro} which is *M in most cases). An example for
Remote Access <tm>:
FILEDOOR.EXE -DD -CFILEDOOR.CF*N -AC:\BBS\FILES\DISP *M
The *N option will be used to select between different FILEDOOR.CF?
files for the different lines. *M is used to swap the largest part
Remote Access to EMS/Disk. When you run a single-line BBS, you can
leave out the *N and use -CFILEDOOR.CFG or even leave that option out
if FileDoor can find the CFG-file on its own.
IMPORTANT: SuperBBS users MUST use the *E options both for a type 7
and a type 15 exit to reload the EXITINFO information back
to the BBS;
When you use a type 15 exit then you must change your batch file in
such a way that after exiting with an errorlevel you jump to the
routine that will start FILEDOOR.EXE. This way you MUST supply all
parameters on the command-line. Also the usage of -R is advised as it
will reload the information from EXITINFO.BBS back to the BBS.
3.2.2 Upload
───────────────────────────────────────────────────────────────────────
When installing FILEDOOR.EXE for uploads in Remote Access, QuickBBS or
SuperBBS as a type 7 exit, the optional datafield should at least
contain the following:
[Drive:\Path\]FILEDOOR.EXE -DU {-U[directory]} {swap-macro}
The -U switch may be omitted when you have set the proper option in
the CFG-file. This also goes for -P (not included above) which can be
set by means of an option in the CFG-file or by using the -P
command-line option.
FileDoor will use all BBS program specific files like FILES.RA in
Remote Access environment to do security locking. As mentioned before
you may also use the switch to swap your BBS program for a large part
to EMS/Disk ({swap-macro} which is *M in most cases). An example for
Remote Access <tm>:
FILEDOOR.EXE -DU -CFILEDOOR.CF*N -UC:\BBS\FILES\UPLOAD *M
The *N option will be used to select between different FILEDOOR.CF?
files for the different lines. *M is used to swap the largest part
Remote Access to EMS/Disk. When you run a single-line BBS, you can
leave out the *N and use -CFILEDOOR.CFG or even leave that option out
if FileDoor can find the CFG-file on its own.
IMPORTANT: SuperBBS users MUST use the *E options both for a type 7
and a type 15 exit to reload the EXITINFO information back
to the BBS;
When you use a type 15 exit then you must change your batch file in
such a way that after exiting with an errorlevel you jump to the
routine that will start FILEDOOR.EXE. This way you MUST supply all
parameters on the command-line. Also the usage of -R is advised as it
will reload the information from EXITINFO.BBS back to the BBS.
3.3 FILEDOOR.CFG
───────────────────────────────────────────────────────────────────────
The FILEDOOR.CFG file is a normal text-file (ASCII-file). You can
create this file with programs like EDLIN or any other normal
ASCII-editor. FileDoor <tm> will search for its CFG-file in the
following way:
- If the -C command-line option is included, this one is used;
- If the environment variable FILEDOOR is set to a directory (not a
filename), FileDoor <tm> will search for FILEDOOR.CFG in that
directory;
- If the environment variable FILEDOOR is set to a path (a filename
and the full path (drive and directory) supplied), FileDoor <tm>
will search for that file;
- If neither -C nor an environment variable is found, FileDoor <tm>
will search in the following order:
- The current directory;
- The DOS-path (DOS 2.xx and higher);
- The directory containing FILEDOOR.EXE (FILE_OVR.EXE) (DOS 3.xx and
higher);
If no CFG-file is found, FileDoor <tm> will terminate abnormally !
For multi-line operations it is advised to use a FileDoor.CFG for
every line you run or to use the special syntax described below.
FILEDOOR.CFG contains many options. Some of them optional, some of
them not. The general format for the FILEDOOR.CFG file is:
Option {line-tag} {parameter} {parameter} ..... {parameter}
There are NO restrictions to the position you start the command, nor
the starting position of the (optional) parameters, but the 'option'
and (if present) the 'parameters' have to be separated with one or
more spaces. You can make any mixture of upper and lower case ! The
{line-tag} MUST start on position 1 of each record !
You can insert comment-lines into your FileDoor.CFG by putting the
%-character on position 1 of the desired line(s). Also empty lines are
considered as comment. It won't take that much longer for FileDoor to
start when there are many comment-lines. The logic of FileDoor will
handle these lines with great speed.
Some of the parameters in the FILEDOOR.CFG file can be overruled with
command-line switches. A generalized example of FILEDOOR.CFG is
included in the release-file. It contains ALL options available in
this release and is called FILEDOOR.CFG (FILEDOOR.MUL also contains
examples for fixed and locked modem, as well as an example of how to
use the {line-tag} options).
The following sub-chapters of 3.3 will contain the several statements
you can use in FILEDOOR.CFG. In the documentation, the statements are
put in logical groups. These groups contain statements with the same
sort of functions. The actual order of the statements in FILEDOOR.CFG
does not matter at all.
In the next pages, I use the following syntax:
[value] : All parameters between '[' and ']' are mandatory. If
'value' is in lower-case, it is a mnemonic. The actual
value is described in the documentation;
[VALUE] : Same as above but when 'VALUE' is in upper-case it is a
real value and should be coded as described (without
the '[' and ']' characters);
{value} : All parameters between '{' and '}' are optional. If
'value' is in lower-case, it is a mnemonic. The actual
value is described in the documentation;
{VALUE} : Same as above but when 'VALUE' is in upper-case it is a
real value and should be coded as described (without
the '{' and '}' characters);
3.3.1 The line-tags
───────────────────────────────────────────────────────────────────────
In a multi-line environment you can choose to use one FileDoor.CFG
file for each line (e.g. FILEDOOR.CF1 for line 1, FILEDOOR.CF2 for
line 2 and so on) or you can create one FILEDOOR.CFG which includes
all the options for ALL lines. In the last case, you MUST include the
-N command-line option in the menu-call for FileDoor <tm>. All options
that are common for all lines can be coded as normal options. Options
for a specific line (like the place and name of the log-files, the
several directories, the modem/protocol options for locked and normal
modems) can be supplied for all different lines. In that case you must
prefix the option with a so called line-tag. The general idea can best
be explained with an example (a little part of a FILEDOOR.CFG file):
[1] System RA1 D:\BBS\RA\FILES.RA
[2] System RA1 D:\BBS\RA\RA2\FILES.RA
FileDoorDir D:\BBS\RA\TXTFILES\
[1] LogFile D:\BBS\RA\LINE01.LOG
[2] LogFile D:\BBS\RA\RA2\LINE02.LOG
Protocol 94 Z U 100 0 ZModem
Usage 0 0 N Y
[1] DSZ D:\BBS\PRO\DSZ.COM port $1 ha on rz -Z -m $M
[2] DSZ D:\BBS\PRO\DSZ.COM port $1 rz -Z -m $M
Protocol 94 Z D 100 0 ZModem
Usage 0 0 N Y
[1] DSZ D:\BBS\PRO\DSZ.COM port $1 ha on sz -Z -k -m $3 $M
[2] DSZ D:\BBS\PRO\DSZ.COM port $1 sz -Z -k -m $3 $M
In the previous example you can see the line-tags ([1] and [2]) for
some of the options. When an option does NOT contain a line-tag, it
will be used for all lines, when an option is prefixed by a line-tag
(like [1] for line 1 and [2] for line 2) it will only be active for
the give line). With this mechanism of line-tags, you can use one
FileDoor.CFG for up to 8 lines !
3.3.2 Very special statements.
───────────────────────────────────────────────────────────────────────
The following statement(s) are very special and should only be used in
very special cases.
┌─────────────────────────────────────────────────────────────────────┐
│ Debug [path] │
└─────────────────────────────────────────────────────────────────────┘
Usage : I have learned from earlier versions that one of the most
difficult problems is to find a specific error. This is
because an unknown number of unknown programs (protocols and
exits) can make use of FileDoor and the basic level of the
common user can vary from poor to very good.
If you ever have a strange problem and the error does not
look obvious, you could consider to set this option on.
[path] must be a drive (optional), directory and filename of
the debug-file to be written. Remember that this file
will NOT be serialized (shared) so you must use a
different file for each different BBS-line (when you
run a multi-line BBS);
Inside the log you can find references to names and values
that will not have much meaning to you, but most important,
you can also find the Bimodem-alike, DSZ-alike and
OPUS-alike log-records (that are normally deleted by
FileDoor after the download).
When reporting an error, I can ask you to send me a part of
the debug-log, so be prepared when you enter a problem to
have a debug-log ready or try to recreate the error first
with the debug-log on. You can always consult me first !
Setting Debug to on means that there is a little drawback in
speed (but not in file-search). Also there can be some extra
disk-access, so the total loss in speed is variable for
every system. I would not advise to set Debug to on as a
default !
Example : Debug C:\SYS\TMP\XFDDEBUG.L01
─────────────────────────────────────────────────────────────
Means : FileDoor will write a debug-log to XFDDEBUG.L01 in the
C:\SYS\TMP directory.
─────────────────────────────────────────────────────────────
┌─────────────────────────────────────────────────────────────────────┐
│ SelMax [maxfiles] │
└─────────────────────────────────────────────────────────────────────┘
Usage : Normally FileDoor will calculate the maximum number of files
that COULD be selected in one execution of FileDoor (with a
maximum of 255). To preserve memory, you can use a lower
number though I should urge you to tell that you should not
make it too low.
[maxfiles] must be set to a value between 1 and 255. By
default FileDoor will try to use 255 entries but
will lower the number by itself when there is not
enough memory.
If the maximum number of files to be selected is reached,
the user will get a warning and the transfer will start at
once. So when you use a value of 1, all protocols can only
transfer 1 file at a time !
Each file-selection entry will need 425 bytes of
conventional memory, so reducing the value to 100 will
reduce the memory requirements with 41.5 Kb.
Example : SelMax 200
─────────────────────────────────────────────────────────────
Means : FileDoor will try to allocate 200 entries (55 less than the
normal value) for file-selection.
─────────────────────────────────────────────────────────────
┌─────────────────────────────────────────────────────────────────────┐
│ NoOwnDSZLog │
└─────────────────────────────────────────────────────────────────────┘
Usage : Normally FileDoor sets the DSZLOG environment variable by
itself. This is needed because FileDoor wants to make sure
that it can examine this log-file.
To do so, FileDoor will alter the environment variable
DSZLOG itself, using some special tricks. Not ALL
DOS-versions allow such tricks (AT&T/Olivetti to name a
few). In these cases you should set the DSZLOG environment
variable yourself and add this option in FILEDOOR.CFG.
Example : NoOwnDSZLOG
─────────────────────────────────────────────────────────────
Means : See description
─────────────────────────────────────────────────────────────
3.3.3 Basic Parameters
───────────────────────────────────────────────────────────────────────
The following statements are more or less basic statements.
┌─────────────────────────────────────────────────────────────────────┐
│ BBSLine [line] │
└─────────────────────────────────────────────────────────────────────┘
Usage : As said before, in multi-line operations, FileDoor must know
the line it is running on. By default, FileDoor uses line 1,
so when you run one single line, both -N and/or this option
can be omitted. There are some reasons to put the line
inside FileDoor.CFG when you run multiple lines:
- There is a flaw in Remote Access with the *N option
that makes the system of generic menu's for all
lines very difficult to use with FileDoor (see chapter
on multi line operations);
- Your command-line is getting to long;
- You can see the which line-number belongs to this CFG file;
[line] must be the BBS-line-number and can be set in the
range from 1 to 99.
Example : BBSLine 3
─────────────────────────────────────────────────────────────
Means : This configuration file is setup for the 3rd BBS-line and all
temporary files will carry this identification.
─────────────────────────────────────────────────────────────
┌─────────────────────────────────────────────────────────────────────┐
│ System [system] [path] │
└─────────────────────────────────────────────────────────────────────┘
Usage : This defines the BBS-system that you use and the path to the
file that contains the file-area information.
[system] must be set to the type of system that you use and
can have the following values:
- RA0 for Remote Access versions up to 0.04, using
the file FILES.RA (0.04 format);
- RA1 for Remote Access versions 1.0x, using the
file FILES.RA (1.0x format);
- RA11 for Remote Access versions 1.1x, using the
file FILES.RA (1.1x format);
- QBBS for QuickBBS 0.xx to 2.74, using the file
FLSEARCH.CTL;
- QNEW for QuickBBS 2.75 and up, using the file
FILECFG.DAT;
- SBBS for SuperBBS 1.1x and up, using the file
FLSEARCH.CTL;
[path] Must point to the complete drive, directory and
filename of the file-area file (see names above) of
the BBS (for this BBS-line);
If you have the idea that the internal format of the area
file has been changed (due to a change of BBS release
number) you are invited to contact the author, so I can add
the newer format ASAP;
Example : System RA11 D:\BBS\RA\FILES.RA
─────────────────────────────────────────────────────────────
Means : You are using a Remote Access <tm> 1.11 (or higher) version
and the area-file for this BBS-line is in D:\BBS\RA and has
the name FILES.RA;
─────────────────────────────────────────────────────────────
┌─────────────────────────────────────────────────────────────────────┐
│ NoAutoUpdate [directory] │
└─────────────────────────────────────────────────────────────────────┘
Usage : Some of the supported BBS programs can reload the
information from EXITINFO.BBS. At this moment the RA 0.04
and higher, the SBBS (with *E used) and QuickBBS 2.75 (and
higher) can do so and the older QuickBBS releases can not.
If your BBS does not support the reload of information from
EXITINFO.BBS or you dislike the direct updates that FileDoor
will perform when the BBS is able to do so, you can set the
NoAutoUpdate option. In this case FileDoor will create a
file called FileDoor.UPD in the CURRENT directory and will
use that file for the user-credits (see chapter on FD_UPD).
[directory] must point to the valid directory that will
contain FILEDOOR.UPD. All lines (if multi-line)
must access the SAME FILEDOOR.UPD otherwise your
users can swap lines and download as many as
[lines] times the number of files as allowed.
NoAutoUpdate is NOT needed for the current (newest) versions
of the supported BBS-programs.
Example : NoAutoUpdate D:\BBS\RA
─────────────────────────────────────────────────────────────
Means : FileDoor will not update the EXITINFO.BBS (alike) file for
this type of BBS but will create a FILEDOOR.UPD file in the
directory D:\BBS\RA.
─────────────────────────────────────────────────────────────
3.3.4 Paths
───────────────────────────────────────────────────────────────────────
The following options will describe the access that FileDoor has to do
on several directories and files.
┌─────────────────────────────────────────────────────────────────────┐
│ FileDoorDir [dir] │
└─────────────────────────────────────────────────────────────────────┘
Usage : If set, FileDoor will search for it's menu and help files in
the supplied path. If not set, FileDoor will create the menu
by its own. Help-files and menu-files must all be put inside
this directory when used. By DEFAULT they must have specific
names but you CAN overrule them with a name you choose by
yourself (see the AnsAsc option).
[dir] This value must point to the directory that contains
all the menu-files (optional) and/or help-files (also
optional). If specific files are not available in this
directory, FileDoor will give an internal message or
will build menus by itself;
Examples of these files are available inside the release
archive. Be sure to update at LEAST the menu-files to the
protocols you use on your own system !
Example : FileDoorDir D:\BBS\RA\TXTFILES
─────────────────────────────────────────────────────────────
Means : Menu/Help files (which are in use) can be found in the
directory D:\BBS\RA\TXTFILES.
─────────────────────────────────────────────────────────────
┌─────────────────────────────────────────────────────────────────────┐
│ UploadPath [dir] │
└─────────────────────────────────────────────────────────────────────┘
Usage : If set, FileDoor will use this directory for uploaded files.
This directory is overruled by the -U[path] on the command-
line that is used to call FileDoor (if available). If this
is the case, FileDoor will not check the UploadPath option
for valid data.
[dir] must point to a valid (available) directory;
Example : UploadPath D:\BBS\RA\FILES\UPLOADS
─────────────────────────────────────────────────────────────
Means : The uploads (normal and/or private) will be put in the
directory D:\BBS\RA\FILES\UPLOADS.
─────────────────────────────────────────────────────────────
┌─────────────────────────────────────────────────────────────────────┐
│ PUploadPath [dir] │
└─────────────────────────────────────────────────────────────────────┘
Usage : If set, FileDoor will use this directory for uploaded files
which are marked private (description starts with /) to the
Sysop. If this option (or -P on the call) is NOT available
but private uploads are allowed, FileDoor will move these
uploads to the normal upload-directory. This directory is
overruled by the -P[path] on the command- line that is used
to call filedoor (if available). If this is the case,
FileDoor will not check the PUploadPath option for valid
data.
[dir] must point to a valid (available) directory;
Example : PUploadPath D:\BBS\RA\FILES\PRIVATE
─────────────────────────────────────────────────────────────
Means : The uploads (only private) will be put in the directory
D:\BBS\RA\FILES\PRIVATE.
─────────────────────────────────────────────────────────────
┌─────────────────────────────────────────────────────────────────────┐
│ DupePath [dir] │
└─────────────────────────────────────────────────────────────────────┘
Usage : If set, FileDoor will move ANY file, marked as a dupe, to
this directory. Normally FileDoor will delete the dupe file.
Even if you use this option, FileDoor will NOT count the
dupe but you can still have a peek at it, because it is not
deleted.
[dir] must point to a valid (available) directory;
Example : DupePath D:\BBS\RA\FILES\DUPES
─────────────────────────────────────────────────────────────
Means : Duplicate uploads are not deleted but moved to the directory
D:\BBS\RA\FILES\DUPES. They are NOT counted !
─────────────────────────────────────────────────────────────
┌─────────────────────────────────────────────────────────────────────┐
│ LogFile [path] │
└─────────────────────────────────────────────────────────────────────┘
Usage : Choose the logfile for logging all Filedoor activities. The
format of the log-file is free and MUST be set with the
special log-file options (see later on). This allows both
standard logging (designed to the same format as the log
that the BBS program makes) and non-standard logging
(something YOU like). The older 2.xx versions of FileDoor
needed a parameter to set the type of log !
[path] must point to a drive (optional), directory and name
of the log-file for this line.
Please remember to point to VARIOUS log-files for each
line you run, unless you want trash in you log or on your
disk.
Example : LogFile D:\LOG\RALIN01.LOG
─────────────────────────────────────────────────────────────
Means : The log-file for this BBS-line is called RALINE01.LOG and
will be written (created) in D:\LOG.
─────────────────────────────────────────────────────────────
┌─────────────────────────────────────────────────────────────────────┐
│ UploadLog [dir] │
│ UploadLog [path] │
└─────────────────────────────────────────────────────────────────────┘
Usage : Sets a special logfile for all uploads including the name of
the uploader. Either use a directory or a fully specified
filename including a path.
[dir] in this form, FileDoor will create a log-file in the
supplied directory under the name FDUPLOAD.LOG;
[path] in this form, you must supply the name of the
log-file, the directory and (optionally) the drive to
use;
Please remember to point to various log-files for each line,
unless you want trash in you log-file or on your disk.
Example : UploadLog D:\LOG\UPLOAD02.LOG
─────────────────────────────────────────────────────────────
Means : Create a log-file for uploads under the name UPLOAD02.LOG in
directory D:\LOG.
─────────────────────────────────────────────────────────────
┌─────────────────────────────────────────────────────────────────────┐
│ PVTUploadLog [dir] │
│ PVTUploadLog [path] │
└─────────────────────────────────────────────────────────────────────┘
Usage : Sets a logfile for PRIVATE uploads including the name of
the uploader. Either use a directory or a fully
specified filename including a path.
[dir] in this form, FileDoor will create a log-file in the
supplied directory under the name PVTUPLOA.LOG;
[path] in this form, you must supply the name of the
log-file, the directory and (optionally) the drive to
use;
Please remember to point to various log-files for each line,
unless you want trash in you log-file or on your disk. This
log-file can be written to the same files as assigned to the
UploadLog option.
Example : PVTUploadLog D:\LOG\PULOAD02.LOG
─────────────────────────────────────────────────────────────
Means : Create a PRIVATE-log (uploads) under the name PULOAD02.LOG in
directory D:\LOG.
─────────────────────────────────────────────────────────────
┌─────────────────────────────────────────────────────────────────────┐
│ DownloadLog [dir] │
│ DownloadLog [path] │
└─────────────────────────────────────────────────────────────────────┘
Usage : Sets a special logfile for all downloads including the name
of the user. Either use a directory or a fully specified
filename including a path.
[dir] in this form, FileDoor will create a log-file in the
supplied directory under the name FDDNLOAD.LOG;
[path] in this form, you must supply the name of the
log-file, the directory and (optionally) the drive to
use;
Please remember to point to various log-files for each line,
unless you want trash in you log-file or on your disk. This
log-file can be the same as assigned in various other
options.
Example : DownloadLog D:\LOG\DNLOAD02.LOG
─────────────────────────────────────────────────────────────
Means : Create a log-file for downloads under the name DNLOAD02.LOG
in directory D:\LOG.
─────────────────────────────────────────────────────────────
┌─────────────────────────────────────────────────────────────────────┐
│ SwapPath [dir] │
└─────────────────────────────────────────────────────────────────────┘
Usage : Sets the directory where FileDoor will place any swap-files.
Only the directory is allowed. FileDoor will generate any
filename by itself, based on the BBS-line and the type of
swap. Remember that there must be at least 200K free on the
disk you point to for every copy of FileDoor that is swapped
(see chapter on swapping).
[dir] must point to a valid (available) directory;
Example : SwapPath E:\ZIP
─────────────────────────────────────────────────────────────
Means : FileDoor will create a swap-file (if needed) in the directory
E:\ZIP.
─────────────────────────────────────────────────────────────
┌─────────────────────────────────────────────────────────────────────┐
│ TempPath [dir] │
└─────────────────────────────────────────────────────────────────────┘
Usage : Set the path where FileDoor will place uploads and temporary
files while work is in progress. FileDoor will put uploads
in a temporary directory first. Also some small files,
depending on the protocol, are placed inside this directory.
You can assign a directory on the same drive as where the
uploads will be put, because FileDoor will use an
intelligent move (move without data transport) when the
temporary- and upload directory are on the same drive.
FileDoor will always create a directory UNDER this directory
to use as the temporary directory and will generate the name
by itself (depending on date/time and BBS line). Best thing
you can do is to let this option point to the same directory
as the up- load directory. FileDoor will remove the
directories that are created UNDER this directory;
[dir] must point to a valid (available) directory;
Example : TempPath D:\BBS\RA\FILES\UPLOADS
─────────────────────────────────────────────────────────────
Means : FileDoor will create temporary (upload) directories under the
directory D:\BBS\RA\FILES\UPLOADS
─────────────────────────────────────────────────────────────
┌─────────────────────────────────────────────────────────────────────┐
│ BimodemCfg [path] │
└─────────────────────────────────────────────────────────────────────┘
Usage : Set the path to the BiModem.Cfg (Bimodem configuration
file). You MUST use this option when you include Bimodem in
the protocols. It must point to the name and location of the
Bimodem.CFG that is used for this (or all) line(s). FileDoor
will use this file as a template for a temporary copy of the
Bimodem.Cfg. Various things (like com-port) are overruled by
FileDoor, so you can use one single (template) Bimodem.CFG.
[path] must point to the drive, directory AND name of the
template BIMODEM.CFG
Example : BimodemCfg D:\BBS\PROTOCOL\BIMODEM.CFG
─────────────────────────────────────────────────────────────
Means : FileDoor will use the BIMODEM.CFG file in D:\BBS\PROTOCOL as
the template for Bimodem transfers.
─────────────────────────────────────────────────────────────
┌─────────────────────────────────────────────────────────────────────┐
│ Verify │
└─────────────────────────────────────────────────────────────────────┘
Usage : When you use Bimodem as one of the protocols (you should
include the previous option), you can either set Bimodem's
file-verify off or on (by including this option).
Example : Verify
─────────────────────────────────────────────────────────────
Means : See description
─────────────────────────────────────────────────────────────
┌─────────────────────────────────────────────────────────────────────┐
│ AlternateFilesPath [dir] │
└─────────────────────────────────────────────────────────────────────┘
Usage : When running with Remote Access 1.xx (or higher), you can
have CD-ROM files with separate FILES.xx files. In RACONFIG
there is an option that will point to the directory that
contains these copies of FILES.xx. Set this option to the
same directory.
[dir] must point to a valid (available) directory;
Example : AlternateFilesPath D:\BBS\RA\ROMFILES
─────────────────────────────────────────────────────────────
Means : FileDoor will search for the FILES.xx files in the directory
D:\BBS\RA\ROMFILES
─────────────────────────────────────────────────────────────
┌─────────────────────────────────────────────────────────────────────┐
│ BADFILESName [dir] │
│ BADFILESName [path] │
└─────────────────────────────────────────────────────────────────────┘
Usage : When your BBS uses the BADFILES.CTL file (see your BBS
documentation), you can use this file as input for FileDoor.
[dir] In this form you only supply the directory where the
BADFILES.CTL is located. FileDoor will append the
name BADFILES.CTL behind the directory you supply;
[path] In this form you supply the full path (so drive,
directory AND name) for the BADFILES.CTL file. This
can be used in case you use a different name for this
file;
The different file-masks from BADFILES.CTL are merged with
the Unwanted options in the FILEDOOR.CFG file. Duplicate
file-masks will be ignored and only stored in memory just
once.
Example : BADFILESName D:\BBS\RA
─────────────────────────────────────────────────────────────
Means : You will use a BADFILES.CTL file that is located in D:\BBS\RA
and has the name BADFILES.CTL.
─────────────────────────────────────────────────────────────
┌─────────────────────────────────────────────────────────────────────┐
│ FILESCTLName [dire] │
│ FILESCTLName [path] │
└─────────────────────────────────────────────────────────────────────┘
Usage : When your BBS uses the FILES.CTL file (see your BBS
documentation), you can use this file as input for FileDoor.
With this option you point to the correct FILES.CTL file.
In this case the FILESCTLName option must either point to
the directory containing FILES.CTL or it must point to a
full filename (path, with drive and directory) that has the
same syntax as the FILES.CTL.
[dir] In this form you only supply the directory where
the FILES.CTL is located. FileDoor will append the
name FILES.CTL behind the directory you supply;
[path] In this form you supply the full path (so drive,
directory AND name) for the FILES.CTL file. This
can be used in case you use a different name for
this file;
{NOTIME} The NOTIME parameter is optional and when supplied
will tell FileDoor that ALL file(s) that are marked
as FREE-files (inside the FILES.CTL, with /FREE as
used parameter), can be downloaded for free EVEN
when there is not enough time left.
The different options from FILES.CTL (free files, password
protected files and unwanted files) are merged with the
FreeFile, PasswordProtect and Unwanted options in the
FILEDOOR.CFG file. Duplicate file-masks will be ignored and
only stored in memory just once.
Example : FILESCTLName D:\BBS\RA NOTIME
─────────────────────────────────────────────────────────────
Means : You will use a FILES.CTL file that is located in D:\BBS\RA
and has the name FILES.CTL. All files marked as free (/FREE)
inside FILES.CTL can be downloaded even when there isn't
enough time.
─────────────────────────────────────────────────────────────
┌─────────────────────────────────────────────────────────────────────┐
│ LIVESYSTEMSPath [dir] │
└─────────────────────────────────────────────────────────────────────┘
Usage : When you use the program USERON by LiveSystems, you can
include this option. It must point to the same directory as
pointed by USERON. In this case, FileDoor will create
entries that can be read by USERON.EXE and that can be
displayed on the BBS. Users on other lines can see the
progress inside FileDoor. You should check the USERON.EXE
program ! It is a nice enhancement to your BBS.
Normally you must point to the so called 'semaphore path' as
supplied in the configuration of Remote Access <tm> (1.1x).
Example : LIVESYSTEMSPath D:\BBS\RA
─────────────────────────────────────────────────────────────
Means : FileDoor will write semaphore files for USERON.EXE in the
directory D:\BBS\RA. USERON.EXE must point to the same
location.
─────────────────────────────────────────────────────────────
┌─────────────────────────────────────────────────────────────────────┐
│ USERONPath [dir] │
│ USERONPath [path] │
└─────────────────────────────────────────────────────────────────────┘
Usage : When you use Remote Access <tm> as the BBS, you can let
FileDoor update the USERON.BBS file. In this case the other
users (other lines) can see that someone is doing a download
or an upload. Normally, FileDoor will use the normal system
directory but in certain cases it can be needed to use this
option to point to that directory or even the full filename.
[dir] In this form you only supply the directory where
the USERON.BBS is located. FileDoor will append the
name USERON.BBS behind the directory you supply;
[path] In this form you supply the full path (so drive,
directory AND name) for the USERON.BBS file. This
can be used in case you use a different name for
this file;
The USERON mechanism of Remote Access is only capable of
showing the type of action (Upload, Download) but not the
progress inside FileDoor. Take a look at the LiveSystems
USERON.EXE program if this is what you like !
Example : USERONPath D:\BBS\RA
─────────────────────────────────────────────────────────────
Means : FileDoor will write semaphores inside the USERON.BBS file in
directory D:\BBS\RA.
─────────────────────────────────────────────────────────────
┌─────────────────────────────────────────────────────────────────────┐
│ USERPath [dir] │
└─────────────────────────────────────────────────────────────────────┘
Usage : FileDoor 3.xx makes it possible to set aside some special
files for a certain user. In this case you must use the
FileUSER and FileMAIN programs to do so. These programs will
place the files in a special directory under a predefined
directory. With the USERPath option you assign this
directory which will be used as the base for all other
(temporary) directories that are created by FILEUSER.EXE.
Even if you do not plan to use the FILEUSER program, you
should set this directory to a location where you (normally)
have some space left. Future versions of FileDoor will make
special usage of this directory !
[dir] must point to a valid (available) directory;
Example : USERPath D:\BBS\RA\USERFILE
─────────────────────────────────────────────────────────────
Means : FileDoor will look for special directories under the supplied
directory D:\BBS\RA\USERFILE. The FileUSER and FileMAIN
programs will also use this option !
─────────────────────────────────────────────────────────────
┌─────────────────────────────────────────────────────────────────────┐
│ ExternalChat [program] {options} │
└─────────────────────────────────────────────────────────────────────┘
Usage : When you include this option, it will be possible to press
ALT-C inside FileDoor to start a chat-program. In this case
the user-time will NOT stop (that will be fixed in a later
version) but you will be able to start a quick chat with the
user.
[program] must be the full name (drive, directory and file)
of the external chat program;
{options} can be one or more options to pass to the external
chat program. Like most of the programs that can
be called from within FileDoor, you can include
macros that will be replaced by actual values when
the program is called. These are:
$C : Will be replaced by the COM-port number
$B : Will be replaced by the BAUD-rate
$T : Will be replaced by the time that is left
for the users session;
$L : Will be replaced by the BBS-line-number
$M : Swap FileDoor from memory before the call
$! : Will force FileDoor to stop the time counting
Example : ExternalChat C:\RA\UTILS\DISPCHAT.EXE /COM$C /QUICK /MULTI
─────────────────────────────────────────────────────────────
Means : FileDoor can call the external chat program DISPCHAT.EXE when
ALT-C is pressed. Some macros will be expanded and passed to
DISPCHAT.EXE.
─────────────────────────────────────────────────────────────
┌─────────────────────────────────────────────────────────────────────┐
│ ExternalView [program] {options} │
└─────────────────────────────────────────────────────────────────────┘
Usage : When the user is selecting files, she/he will get the option
to view files. FileDoor's internal view is limited to the
display of filenames inside archives but you can add an
external view program like DISP's MTS.EXE to view inside the
files as well. If you would like to do so, you need to add
this option to FILEDOOR.CFG.
[program] must be the full name (drive, directory and file)
of the external view program;
{options} can be one or more options to pass to the external
view program. Like most of the programs that can
be called from within FileDoor, you can include
macros that will be replaced by actual values when
the program is called. These are:
$C : Will be replaced by the COM-port number
$B : Will be replaced by the BAUD-rate
$T : Will be replaced by the time that is left
for the users session;
$F : Will be replaced with the full path to the
file that must be viewed;
$L : Will be replaced by the BBS-line-number
$M : Swap FileDoor from memory before the call
When you want to include MTS.EXE into this option, you need
at least the 7.59 version (a pre 8.01 version) or all 8.0x
versions or higher ! Lower versions can not work with single
files, nor can they display non-archived files.
Example : ExternalView C:\RA\UTILS\MTS.EXE /L$L /F$F
─────────────────────────────────────────────────────────────
Means : MTS.EXE (in C:\RA\UTILS) is called for viewing files. The $L
will be expanded to the BBS-line number and the $F will be
expanded to the full path to the file.
─────────────────────────────────────────────────────────────
3.3.5 Statements that define the logging format
───────────────────────────────────────────────────────────────────────
In general, FileDoor can write log-records to 3 different log-files
with a fully free format. The three logs are:
- System log
Over here FileDoor will write records for uploaded and
downloaded files (e.g. the log-file that the BBS program also
maintains);
- User upload-log
Over here FileDoor will write records for uploaded files;
- User download-log
Over here FileDoor will write records for downloaded files;
As told, you can use a free format of the log-records for any of the
three files BUT it is advised to make the records in the system-log of
the same format as the actual records, created by the BBS program. In
this way, log-file analyze programs can include these records as if
they were from the BBS itself. The other two logs can be coded in a
free style UNLESS you use a third-party log-analyze program that also
included these FileDoor-specific log-files.
One major and VERY important aspect of the next options is, that if
you do not define them (while having the LogFile, Downloadlog and/or
Uploadlog options active), FileDoor will write EMPTY lines in one or
more of these logs. To be more specific:
- When LogFile is set, BBSDNFormat and BBSUPFormat must also be set;
- When DownloadLog is set, UseDNFormat must also be set;
- When UploadLog is set, UseUPFormat must also be set;
- When a ???DNFormat or ???UpFormat (where ??? is BBS or USE) is set,
you will also have to set ???DateFormat and ???TimeFormat, otherwise
there is no date/time stamping in the log-file.
The following options are available (note that in the supplied file
FILEDOOR.CFG, examples are present for the major BBS types).
┌─────────────────────────────────────────────────────────────────────┐
│ BBSDNFormat [Format] │
│ BBSUpFormat [Format] │
└─────────────────────────────────────────────────────────────────────┘
Usage : These two options define the format of the records in the
BBS-log (e.g. the file you point to, using the LogFile
option) for Download (BBSDNFormat) and Upload (BBSUPFormat).
[format] is a line with text and/or macro's supplied by you
and (when macro's are used) replaced by real text by the
FileDoor program at run-time. All spaces must be replaced
with an underscore ('_') character (so [format] is one line
without any spaces in it). You can use any of the following
macro's inside your format-line:
%D will be replaced with the date. To use this macro, you
must also set the BBSDateFormat in your configuration
file (see later for a description of this option);
%T will be replaced with the time. To use this macro, you
must also set the BBSTimeFormat in your configuration
file (see later for a description of this option);
%L will be replaced with the letter of the protocol as you
have defined in the PROTOCOL option of that protocol;
%N will be replaced with the comment belonging to the
protocol and as defined in the PROTOCOL option for that
protocol (eg. 'ZModem the best !');
%U will be replaced with the name of the user who downloaded
or uploaded the file;
%P will be replaced with the filename AND path of the file
that was download or uploaded (for uploads ALWAYS the
normal upload path);
%F will be replaced with the filename of the file that was
download or uploaded (no paths);
%X will be replaced with *DUPE* if the file was a dupe at
upload.
%B will be replaced with the filesize (in bytes) of the file
in question;
%K will be replaced with the filesize (in KBS) of the file
in question;
^M will be expanded to a CR+LF sequence in the log-file;
A remark on the %X option. If you do NOT include it in the
BBSUPFormat statement, no log-records will be created for
dupes (this is normally the case). If you like a record of
your dupes, you can either use the %X in the UseUPFormat
statement or even include it in the BBSUpFormat option, but
remember that logfile analyze programs can have problems
with it;
Example : BbsDNFormat +_%D_%T_FDOR_Download_[%L]_%P
─────────────────────────────────────────────────────────────
Means : That a log-record is generated with a format that looks like:
28-Aug-91 21:00 FDOR Download [Z] C:\ZIP\DOAFILE.NOW
The date and time are generated from the BBSDateFormat and
BBSTimeFormat options.
─────────────────────────────────────────────────────────────
┌─────────────────────────────────────────────────────────────────────┐
│ BBSDateFormat [Format] │
└─────────────────────────────────────────────────────────────────────┘
Usage : In the BBSDNFormat and BBSUpFormat, you can use the %D macro
that will be replaced with the date. To let this actually
happen, you must define HOW the date will look like. To
define this, you must use this option. [format] is the
format of the date. It will be composed of special macro's
and some text added by you. The following macro's are
available:
dd : replaced with the day (leading zeroes);
DD : replaced with the day (leading spaces);
mm : replaced with the month (leading zeroes);
MM : replaced with the month (leading spaces);
yy : replaced with the year (leading zeroes);
YY : replaced with the year (leading spaces);
nnn : replaced with the name of the month (format Jan);
NNN : replaced with the name of the month (format JAN);
www : replaced with the name of the day (format Mon);
WWW : replaced with the name of the day (format MON);
Further you can use '-' or '/' to separate the different
digits. In [format] any spaces must be replaced with an
underscore character.
Example : BbsDateFormat dd-nnn-yy
─────────────────────────────────────────────────────────────
Means : Will be expanded to 01-Aug-91 (depending on the date)
─────────────────────────────────────────────────────────────
┌─────────────────────────────────────────────────────────────────────┐
│ BBSTimeFormat [Format] │
└─────────────────────────────────────────────────────────────────────┘
Usage : In the BBSDNFormat and BBSUpFormat, you can use the %T macro
that will be replaced with the time. To let this actually
happen, you must define HOW the time will look like. To
define this, you must use this option. [format] is the
format of the time. It will be composed of special macro's
and some text added by you. The following macro's are
available:
hh : replaced with the hour (leading zeroes);
HH : replaced with the day (leading spaces);
mm : replaced with the min (leading zeroes);
MM : replaced with the min (leading spaces);
ss : replaced with the sec (leading zeroes);
SS : replaced with the sec (leading spaces);
t : replaced with the 'a' or 'p' for 'am' and 'pm'
e : replaced with the 'm' from 'am' or 'pm'
Further you can use ':' or ' ' to separate the different
digits. In [format] any spaces must be replaced with an
underscore character.
Example : BbsTimeFormat hh:mm:ss
─────────────────────────────────────────────────────────────
Means : Will be expanded to 21:00:01 (depending on the time)
─────────────────────────────────────────────────────────────
┌─────────────────────────────────────────────────────────────────────┐
│ UseDNFormat [Format] │
│ UseUpFormat [Format] │
└─────────────────────────────────────────────────────────────────────┘
Usage : These two options define the format of the records in the
log pointed by DownloadLog (UseDNFormat) and UploadLog
(UseUPFormat). They work the same as the BBSDNFormat and
BBSUPFormat options !
Example : See BBSDNFormat
─────────────────────────────────────────────────────────────
Means : See BBSDNFormat
─────────────────────────────────────────────────────────────
┌─────────────────────────────────────────────────────────────────────┐
│ BBSMAFormat [Format] │
└─────────────────────────────────────────────────────────────────────┘
Usage : This option does the same as the BBDSNFormat option but is
used for the FILEMAIN program. You can now add a different
log-format for entries made by FILEMAIN.EXE.
Example : See BBSDNFormat
─────────────────────────────────────────────────────────────
Means : See BBSDNFormat
─────────────────────────────────────────────────────────────
┌─────────────────────────────────────────────────────────────────────┐
│ UseDateFormat [Format] │
└─────────────────────────────────────────────────────────────────────┘
Usage : Used for the date format in the UseUPFormat and UseDNFormat
options. The same as BBSDateFormat.
Example : See BBSDateFormat
─────────────────────────────────────────────────────────────
Means : See BBSDateFormat
─────────────────────────────────────────────────────────────
┌─────────────────────────────────────────────────────────────────────┐
│ UseTimeFormat [Format] │
└─────────────────────────────────────────────────────────────────────┘
Usage : Used for the time format in the UseUPFormat and UseDNFormat
options. The same as BBSTimeFormat.
Example : See BBSTimeFormat
─────────────────────────────────────────────────────────────
Means : See BBSTimeFormat
─────────────────────────────────────────────────────────────
3.3.6 Other statements, not related to protocol definition
───────────────────────────────────────────────────────────────────────
In this chapter a lot of special options are described that will have
some meaning on the working, the 'looks' and 'feel' of FileDoor.
┌─────────────────────────────────────────────────────────────────────┐
│ Color [lowmenu] [highmenu] [attention] [statusbar] [errors] │
│ [text] [size UnC] [Size Com] [date] [time] │
└─────────────────────────────────────────────────────────────────────┘
Usage : You can overrule the default colors to make FileDoor look
more the way your own BBS looks. There are 10 items that can
be overruled. They are the menu-color (low) [lowmenu], the
[lowmenu] The (low) color of the menu entries;
[highmenu] The (high) color of the menu entries;
[attention] The color of important highlighted fields;
[statusbar] The color of the local status-bar;
[errors] The color of the errors (when displayed);
[text] The color for various texts;
[size unC] The color for uncompressed sizes (internal view);
[size Com] The color for compressed sizes (internal view);
[date] The color for dates (internal view);
[time] The color for times (internal view);
The last 5 colors are only used inside the <V> and <I>
options in the download selection menu.
Each of these variables must be coded when Color (or Colour)
is used. They must contain a number between 0 and 255. The
color you want to use is made up with the following formula:
[foreground-color] + (16 * [background-color]) (noblink)
or
[foreground-color] + (16 * [background-color]) + 128 (blink)
[Foreground-color] can be a number from 0 to 15, and the
[background-color] can be a number from 0 to 7. When you use
higher numbers on background-color (8 to 15), you get
blinking reversed text (not nice).
The numbers 0 to 15 stand for:
0 = Black 8 = DarkGray
1 = Blue 9 = LightBlue
2 = Green 10 = LightGreen
3 = Cyan (sea ) 11 = LightCyan
4 = Red 12 = LightRed
5 = Magenta (purple) 13 = LightMagenta (light purple)
6 = Brown (orange) 14 = Yellow
7 = LightGray 15 = White
So to create a cyan on black item, this will come to 3 + (16
* 0) = 3 and for a white on red text this will come to 15 *
(16 * 4) = 79. For blinking, add 128 to the number.
Example : Color 2 10 14 47 12 6 7 8 4 12
─────────────────────────────────────────────────────────────
Means : Create a 'green based' FileDoor
─────────────────────────────────────────────────────────────
┌─────────────────────────────────────────────────────────────────────┐
│ HelpExitKeys [helpkey] [exitkey] │
└─────────────────────────────────────────────────────────────────────┘
Usage : Normally, FileDoor uses the '?' key for help and the '-' key
to terminate (both in the protocol selection menu). If you
would like some other characters (like 'H' and 'Q') you can
include them in the HelpExitKeys option. ALWAYS define this
option BEFORE any PROTOCOL option because FileDoor checks to
see if there are duplicate keys used for different protocols
and/or functions.
[helpkey] is the key you plan to use for help-information in
the protocol menu (normally ?);
[exitkey] is the key you plan to use to exit from the
protocol menu (normally -).
Example : HelpExitKeys H Q
─────────────────────────────────────────────────────────────
Means : Use H for help en Q to exit inside the protocol menu
─────────────────────────────────────────────────────────────
┌─────────────────────────────────────────────────────────────────────┐
│ StatusLine │
└─────────────────────────────────────────────────────────────────────┘
Usage : FileDoor can supply a status-line at the bottom of the
display. Some SysOps like it, some don't. If you want to
have a full status-line at the bottom, you should include
this option, otherwise you won't get a status-line. With
large displays and when you display many ANS/ASC files, the
status-line can slow the speed somewhat (no visual change on
a 16800 connection though).
Example : StatusLine
─────────────────────────────────────────────────────────────
Means : See description
─────────────────────────────────────────────────────────────
┌─────────────────────────────────────────────────────────────────────┐
│ NoDupeStat │
└─────────────────────────────────────────────────────────────────────┘
Usage : FileDoor will display a little progress-bar on the remote
(and local) screen when it is searching for duplicate files.
If you dislike the looks of it, you can remove it by adding
this option to FILEDOOR.CFG.
Example : NoDupeStat
─────────────────────────────────────────────────────────────
Means : See description
─────────────────────────────────────────────────────────────
┌─────────────────────────────────────────────────────────────────────┐
│ NoFindStat │
└─────────────────────────────────────────────────────────────────────┘
Usage : FileDoor will display a little progress-bar on the remote
(and local) screen when it is searching for selected files.
If you dislike the looks of it, you can remove it by adding
this option to FILEDOOR.CFG.
Example : NoFindStat
─────────────────────────────────────────────────────────────
Means : See description
─────────────────────────────────────────────────────────────
┌─────────────────────────────────────────────────────────────────────┐
│ MenuIfOnlyOne │
└─────────────────────────────────────────────────────────────────────┘
Usage : If you include only ONE protocol (f.i. Zmodem and no other
protocols), FileDoor can go directly into the file-selection
menu without displaying the protocol-menu (why should you
need a menu when there is only one choice). If you still
want to have the menu (f.i. to give the user the chance to
exit in simple way), you must add this option. In that case
FileDoor will display the protocol-menu with the one and
only choice available to the user.
Example : MenuIfOnlyOne
─────────────────────────────────────────────────────────────
Means : See description
─────────────────────────────────────────────────────────────
┌─────────────────────────────────────────────────────────────────────┐
│ ForceEdit │
└─────────────────────────────────────────────────────────────────────┘
Usage : If the user supplies the comment for an upload file BEFORE
the transfer, FileDoor will not ask for that comment again
AFTER the transfer unless it is too small. The user can
supply comments in two ways:
- In FileDoor's upload menu;
- While inside Bimodem <tm>, in which case Bimodem will send
the comment along with the file;
If you include the ForceEdit option, the user will still
have to press ENTER on every comment AFTER the transfer,
even if there is a complete comment available. Without the
option, FileDoor will not ask for input anymore and will
take the (already) supplied comment as-is.
Example : ForceEdit
─────────────────────────────────────────────────────────────
Means : See description
─────────────────────────────────────────────────────────────
┌─────────────────────────────────────────────────────────────────────┐
│ InternalOverUser │
└─────────────────────────────────────────────────────────────────────┘
Usage : When you run specific programs inside your ExitAfterUploadx
exit(s) like DISP's MTA.EXE, it is possible to obtain the
comment from files like FILE_ID.DIZ files and pass them from
MTA.EXE to FileDoor. If you install MTA.EXE and FILEDOOR.EXE
in this way, you have the following choices:
- FileDoor will always take the comment obtained by MTA if
it is present, otherwise it will ask for a comment. If the
user supplied a comment before the transfer, it is
overwritten by the comment obtained from the exit (MTA).
FileDoor only works in this way when you add the option
InternalOverUser into FILEDOOR.CFG;
- If you do NOT add the InternalOverUser option, FileDoor
will use the comment supplied by the user before the
transfer (if any) and if there was not such a comment,
FileDoor will take the comment from the exit (if any);
Example : InternalOverUser
─────────────────────────────────────────────────────────────
Means : See description
─────────────────────────────────────────────────────────────
┌─────────────────────────────────────────────────────────────────────┐
│ NotAvailText [text] │
└─────────────────────────────────────────────────────────────────────┘
Usage : On two places FileDoor reports '[FileDoor] no description
available'. This is while in the file-selection display and
in the information file, when a file has no description
inside the FILES.BBS (unless HideFiles prevents FileDoor
from reporting the file at all). You can alter this text to
any text you like yourself.
[text] is the new text that is used as a replacement for the
default text. It can be up to 47 characters and all
spaces must be codes as underscore characters.
Example : NotAvailText For_this_file_there_is_no_comment
─────────────────────────────────────────────────────────────
Means : Will for FileDoor to put 'For this file there is no comment'
inside the screens when there is no comment in FILES.BBS
available.
─────────────────────────────────────────────────────────────
┌─────────────────────────────────────────────────────────────────────┐
│ ANSASC [type] [name] │
└─────────────────────────────────────────────────────────────────────┘
Usage : By default, FileDoor will use a number of standard
ANSI/ASCII files on certain occasion. These files must be
located in the directory pointed to by the FileDoorDir
option. These files have standard names which can conflict
with names that you already use for other programs (doors,
BBS itself and so on).
The ANSASC options give you the chance to overrule the names
of one or more of the standard ANSI/ASCII files that
FileDoor needs.
[type] must be a 2-character code of the filename you want
to alter (see below);
[name] must be a 1 to 8 character (new) name that you want
to assign (see below for the internal FileDoor
default names);
The following ANSI/ASCII files are used by FileDoor and can
be overruled with other names:
[type] [name] [description]
-------------------------------------------------------------
HU HLP_UP Help file for uploads
HD HLP_DOWN Help file for downloads
HT HLP_TAGS Help file for tagging options
HS HLP_SELE Help file for file-selection
HP HLP_SUPL Help file for upload specification
UW HLP_UNWA Help file with unwanted reject reason
0B HLP_EMPT Help file with 0-bytes reject reason
OL HLP_TOLD Help file with too-old reject reason
RJ HLP_REJE Help file with description of reject reason
DU HLP_DUPE Help file with duplicates reject reason
NA HLP_NARC Help file with non-archive reduction reason
UT HLP_UTNX Help file with 'THANKS FOR UPLOAD' text
GB GOODBYE Help file to display before internal logoff
MU MNU_UP External menu-file for uploads
MD MNU_DOWN External menu-file for downloads
EM ERR_10FL External error-text with 10 or more errors
ES ERR_SELF External error-text with already sel. file
ER ERR_RATI External error-text when denied by ratio
ED ERR_DLIM External error-text when denied by limits
ET ERR_SEST External error-text when denied by time
EX ERR_EXIT External error-text when denied by exit
-------------------------------------------------------------
You should examine the supplied examples. Normally the
ERR*.* files must be created without a clear-screen because
they are put under the current text. Looking at the examples
will give you a good clue.
If you don't want to use one or more help/menu/error texts
from ANSI/ASCII texts, you can supply a non-existing name
like RIDINGH.OOD in which case FileDoor will display its
internal text (quicker but less nice).
FileDoor makes no usage (yet) of special codes inside the
ANSI-files as the BBS program does. In most cases this means
that you must overrule the GOODBYE file with one of you own
because most SysOp's have put some extended ANSI codes in
this screen to display the users name, the time and so on.
Example : AnsAsc HU MYHELP_U (look for MYHELP_U.A?? and not HLP.UP.A??)
Example : AnsAsc GB XFGOODB (look for XFGOODB.A?? and not GOODBYE.A??)
─────────────────────────────────────────────────────────────
Means : Overrule name for the GOODBYE screen (normally GOODBYE.Axx)
with XFGOODB. FileDoor will now look for XFDOODB.Axx !
─────────────────────────────────────────────────────────────
┌─────────────────────────────────────────────────────────────────────┐
│ AutoSearch │
└─────────────────────────────────────────────────────────────────────┘
Usage : If set, a global transfer will be enabled. All file areas
will be searched for the wanted file(s). Full security and
flag support will prevent users from downloading files from
areas they don't have access to.
Example : AutoSearch
─────────────────────────────────────────────────────────────
Means : See description
─────────────────────────────────────────────────────────────
┌─────────────────────────────────────────────────────────────────────┐
│ DownloadInfo [file] {default} │
└─────────────────────────────────────────────────────────────────────┘
Usage : FileDoor contains an option to ask the user if she/he wants
the comments for the downloaded files copied from your own
FILES.BBS's to a special file that can be downloaded. The
user can enter /INFO in the selection option or FileDoor will
add the download information by itself (when using a batch
protocol).
If you would like your users to have this option, you must
create a text-file that contains the header of the file that
is sent when the user selects /INFO. You can include a
commercial or some information of interest.
The temporary file for the user is created in the same
directory that contains [file] and is deleted when the user
exits from FileDoor (even when the file was not downloaded
at all).
The user will receive a file in the FILES.BBS style and as a
service, your files-counter (if defined in FileDoor) is
removed from the comment. The comment can be up to 240 bytes
in length and FileDoor will be able to support the QFV/C/F
<tm> +-comment-lines in your FILES.BBS.
[file] must point to a text-file. The parameter must
contain the drive, directory and filename of the
file;
{default} can either be set to Y or N. When the user gets
the question if she/he wants to include the
download-info file, the value of this parameter
will rule the assigned default when the user hits
the [ENTER] key. If Y, [ENTER] will assign a 'Y',
otherwise the default will be N.
Example : DownloadInfo D:\BBS\RAX\XFDFBBSI.TXT Y
─────────────────────────────────────────────────────────────
Means : D:\BBS\RAX\XFDFBBSI.TXT contains the commercial (or info)
that will be the header of the information-file that the
user will receive (when asked). The default answer (when
the user presses [ENTER]) is 'Y'es.
─────────────────────────────────────────────────────────────
┌─────────────────────────────────────────────────────────────────────┐
│ ExactMatch │
└─────────────────────────────────────────────────────────────────────┘
Usage : If set, FileDoor will not ask questions when an exact match
between mask and filename (e.g. the mask does not contain
wildcards) is found. Also searching for other files with
this mask is also disabled. Other masks will still be
searched for and everything stays the same as before when a
user includes wildcards in the mask. See chapter 4.5 for a
discussion on file selection.
Example : ExactMatch
─────────────────────────────────────────────────────────────
Means : See description
─────────────────────────────────────────────────────────────
┌─────────────────────────────────────────────────────────────────────┐
│ QuickMatch │
└─────────────────────────────────────────────────────────────────────┘
Usage : If set, FileDoor will not ask questions when a match is
found (e.g. the first match) independent of the fact if the
user used wildcards in the mask. See chapter 4.5 for a
discussion on file selection.
Example : QuickMatch
─────────────────────────────────────────────────────────────
Means : See description
─────────────────────────────────────────────────────────────
┌─────────────────────────────────────────────────────────────────────┐
│ HideFiles [highsec] {lowsec} │
└─────────────────────────────────────────────────────────────────────┘
Usage : This (optional) feature can be used for files that are not
reported in the FILES.BBS file. With this option you can make
a difference between your 'normal' guests, your 'new' guests
and those that you don't want to loose for any money.
[highsec] This must be a security-level. All user with this
level (and above) will see files, not reported in
FILES.BBS, while they are selecting files. They can
also select the files;
{lowsec} This parameter is optional. If set, all users with
this security level or higher (but lower than
[highsec] can SELECT files not reported inside
FILES.BBS but ONLY when they supply the exact
file-name (no wildcard). With a wildcard
file-search, they will not be shown to those users;
If you only set [highsec], all users with a lower level than
[highsec] are not able to select nor see the files that are
NOT reported in FILES.BBS.
Example : HideFiles 10000 100
─────────────────────────────────────────────────────────────
Means : Only users with level 10000 or above can see and select
files which are NOT in FILES.BBS. All users with level
100 to 9999 can select (and see) files which are not in
FILES.BBS if they supply the EXACT name;
─────────────────────────────────────────────────────────────
┌─────────────────────────────────────────────────────────────────────┐
│ FilesCount {format} │
└─────────────────────────────────────────────────────────────────────┘
Usage : If used, after a download, all FILES.BBS files will have the
right file-counters updated. In this way, you will be able
to track the number of downloads of each file in your
library.
{format} indicates the number of digits used in your files
counter AND the characters that incapsulate the
counter. You can use @ or # for the counter, where
@ will cause tailing zeroes and # will cause
tailing spaces and any combination of incapsulation
characters. If {format} is left out, [@@] is the
used default.
FileDoor uses a smart update. Downloads of multiple files
are collected and FILES.BBS is opened only once.
Example : FilesCount [@@@] (will cause [001] xxxxx)
─────────────────────────────────────────────────────────────
Means : [001] will be added to the FILES.BBS when this is the first
download.
─────────────────────────────────────────────────────────────
┌─────────────────────────────────────────────────────────────────────┐
│ UploadName [place] │
└─────────────────────────────────────────────────────────────────────┘
Usage : If used, FileDoor will place the name of the uploader into
the FILES.BBS entry that it will create for the uploaded
file(s).
[place] can be either F, B, + or +D. If 'F' is used,
FileDoor will place the uploaders name in front of
the comment (behind any optional file-counter). If
'B' is used, FileDoor will place the name BEHIND the
comment. If '+' is used, FileDoor will create a
DISP-compatible +-comment-line in the FILES.BBS with
the name of the uploaded. The same goes for +D but
in this case also the date will be added to the name
of the uploader.
The format of the name depends on the [place] parameter.
Here are some examples from FILES.BBS with the different
[place] options:
Using 'F' : ALLFILES.ZIP [Rob van.hoeven] My allfiles
or
ALLFILES.ZIP [000] [Rob van.hoeven] My allfiles
Using 'B' : ALLFILES.ZIP My allfiles [Rob van.hoeven]
or
ALLFILES.ZIP [000] My allfiles [Rob van.hoeven]
Using '+' : ALLFILES.ZIP My allfiles
+Uploaded by: Rob van.hoeven
or
ALLFILES.ZIP [000] My allfiles
+Uploaded by: Rob van.hoeven
Using '+D': ALLFILES.ZIP My allfiles
+Uploaded by: Rob van.hoeven on mm/dd/yy hh:mm
or
ALLFILES.ZIP [000] My allfiles
+Uploaded by: Rob van.hoeven on mm/dd/yy hh:mm
As you can see, there are a number of possible entries. You
should remember that FileDoor will subtract the length of
the user's name from the comment-length when using the F or
B parameters. This can result in very short descriptions.
Example : UploadName +
─────────────────────────────────────────────────────────────
Means : See description
─────────────────────────────────────────────────────────────
┌─────────────────────────────────────────────────────────────────────┐
│ CommentLength [option1] [option2] │
└─────────────────────────────────────────────────────────────────────┘
Usage : This will define the minimum and maximum length of the
file-descriptions for uploaded files. You must supply the
real minimum and maximum length including the files-counter.
Defaults are 20 and 47. You can define a length up to 240
characters.
[option1] is a numeric digit (20 or more) of the minimum
length of the file-comment;
[option2] is a numeric digit (21 to 240) of the maximum
length of the file-comment;
Example : CommentLength 20 47
─────────────────────────────────────────────────────────────
Means : Comments that are supply must be at least 20 bytes and can
not exceed 47 characters !
─────────────────────────────────────────────────────────────
┌─────────────────────────────────────────────────────────────────────┐
│ FreeFile [mask] {NOTIME} │
│ FreeFile [path] {NOTIME} │
└─────────────────────────────────────────────────────────────────────┘
Usage : If set, FileDoor will not calculate the kB's downloaded for
the supplied file names.
[mask] In this form, FreeFile works GLOBALLY on all areas.
[mask] is a file-mask (wildcards are allowed) and
marks all files that won't be counted for DOWNLOAD;
[path] In this form, FreeFile works LOCALLY for the mask
you supply and only in the directory you supply.
[path] must be a drive (optionally), directory and
file-mask (wildcards allowed) that marks the
file(s) that won't be counted for DOWNLOAD;
{NOTIME} The NOTIME parameter is optional and when supplied
will tell FileDoor that the file(s) that match the
previous [mask] or [path] can be selected (for
free) EVEN if there isn't enough time for download.
This can be useful for new users who can download
the ALLFILES or BBS-manual while the can only stay
a short while on the BBS;
File-masks that are supplied with FreeFile options (up to
255 of each type, so 255 without directory and 255 with)
will be merged with those that come from FILES.CTL (if you
use that file and have assigned it with the FILESCTLPath
option).
Example : FreeFile D:\BBS\RAX\FILE\DISP\MT*.* NOTIME
─────────────────────────────────────────────────────────────
Means : All files with file-mask MT*.* in D:\BBS\RAX\FILE are free
for download, even when there isn't enough time to download
the file.
─────────────────────────────────────────────────────────────
┌─────────────────────────────────────────────────────────────────────┐
│ ExcludeFile [mask] │
│ ExcludeFile [path] │
└─────────────────────────────────────────────────────────────────────┘
Usage : Normally FileDoor will display ALL files that match the
users selection (provided the security level is ok). Only
when you use the HideFiles option, files, not inside the
FILES.BBS file, will not be shown.
When you do not include HideFiles and you don't use the
ExcludeFile option, FileDoor will also show files like
FILES.BBS, DIR.BBS, PFILES.BBS (and their BAK versions) and
more of these files that are present in all areas but of no
use for the user.
You can use the ExcludeFile option (up to 255 of each type)
to exclude these global files.
[mask] In this form, you supply a file-mask (wildcards are
allowed) of files that you don't want to show up in
ANY of the areas (GLOBAL option);
[path] In this form, you supply a file-mask with a drive
(optional) and directory (mandatory) of file(s) that
you don't want to show up in a specific area (LOCAL
option).
You should AT LEAST include options to exclude FILES.*,
PFILES.* and DIR.* unless you make it possible to download
these files.
Example : ExcludeFile FILES.*
─────────────────────────────────────────────────────────────
Means : FileDoor will not show files which match FILES.* (like the
FILES.BBS, FILES.BAK, FILES.MTA and so on) in any area. They
can also not be selected for download.
─────────────────────────────────────────────────────────────
┌─────────────────────────────────────────────────────────────────────┐
│ DefaultExtension [extension] │
└─────────────────────────────────────────────────────────────────────┘
Usage : Set the default extension for wildcards or partial
filenames. This will also be displayed in the file
selection part of FileDoor. If no extensions are used in
your file-base remember to set [extension] to '*'. When set
to ZIP (for example), a filename MYBBS* will be expanded to
MYBBS*.ZIP and FileDoor will search for that file. If the
user enters any extension or wildcard as extension, none is
added by FileDoor.
[extension] must by the 1 to 3 digit extension that is the
most frequently used extension on your BBS.
You can supply up to 5 different DefaultExtension options in
FILEDOOR.CFG. FileDoor will check all eligible files with
the supplied extensions.
Example : DefaultExtension ZIP
─────────────────────────────────────────────────────────────
Means : If a user enters ALLFILES, FileDoor will search for a file
called ALLFILES or ALLFILES.ZIP.
─────────────────────────────────────────────────────────────
┌─────────────────────────────────────────────────────────────────────┐
│ Unwanted [mask] │
└─────────────────────────────────────────────────────────────────────┘
Usage : Set any filename or extension that is unwanted for an
upload on your system. There can be up to 100 Unwanted
options all together.
[mask] is the file-mask (wildcards allowed) of files that
are unwanted.
Be warned. The /UNWANTED files from FILES.CTL and the files
from BADFILES.CTL are also added to the range of unwanted
files. Each is counted as a normal Unwanted option !
Example : Unwanted ARJ2??.*
─────────────────────────────────────────────────────────────
Means : If a file that matches this mask is uploaded or given as an
upload, FileDoor will mark it as unwanted and reject the
file (after transfer it is removed and not counted).
─────────────────────────────────────────────────────────────
┌─────────────────────────────────────────────────────────────────────┐
│ NoArchiveCredit [amount] │
└─────────────────────────────────────────────────────────────────────┘
Usage : Set the credit for non-archived files. FileDoor will test
the uploaded file for any known compression method. The
calculation is as follows: (filesize / 100) *
NoArchiveCredit. You do not have to tell FileDoor the
extensions or archives, because FileDoor will look inside
any uploaded file by itself and will detect ARC, PAK, PKA,
ZOO, ZIP, ARJ, LU, DWC, MD, HYPER, LHA, LHarc and LArc files
by itself (normal and SFX files).
NoArchiveCredit runs BEFORE the ULMultiply option so before
any added credits are calculated, FileDoor will first reduce
the base-credits for non-archived files.
Example : NoArchiveCredit 50
─────────────────────────────────────────────────────────────
Means : If a non-archive file is uploaded, FileDoor will only count
50% of the size as credits.
─────────────────────────────────────────────────────────────
┌─────────────────────────────────────────────────────────────────────┐
│ Delete0ByteFiles │
└─────────────────────────────────────────────────────────────────────┘
Usage : If this option is used, FileDoor will remove all UPLOADED
files with a length of 0 bytes. The user will be informed
and the file is not counted as upload (ratio!).
Example : Delete0ByteFiles
─────────────────────────────────────────────────────────────
Means : See description
─────────────────────────────────────────────────────────────
┌─────────────────────────────────────────────────────────────────────┐
│ DelOldFiles [mm/dd/yy] │
└─────────────────────────────────────────────────────────────────────┘
Usage : If this option is used, FileDoor will remove all UPLOADED
files that have an INTERNAL date lower than mm/dd/yy. The
internal date is calculated by looking at all files inside
archives (if it is an archive) and picking the highest date
inside the archive as the date to compare. For non-archive
files, FileDoor will look at the normal date/time stamp but
that doesn't always work OK, because some protocols stamp
the newly uploaded file with the date/time of today.
[mm/dd/yy] must be a valid date after which files will be
deleted.
The user will be notified that the file will be deleted and
is not credited for the file.
Example : DelOldFiles 01/01/90
─────────────────────────────────────────────────────────────
Means : Any file that is dated before 01/01/90 is removed from the
upload and not counted. For archives, FileDoor will look
inside the archive. The highest date inside the archive is
matched with the date on DelOldFiles.
─────────────────────────────────────────────────────────────
┌─────────────────────────────────────────────────────────────────────┐
│ DelAfterDl [mask] │
└─────────────────────────────────────────────────────────────────────┘
Usage : This is a very tricky option. There can be up to 100 of
these options. If a file is downloaded that matches [mask]
on one (or more) of the DelAfterDL options, the file is
DELETED after a successful download ! It is obvious that you
must NOT include a DelAfterDL *.* option in your
FILEDOOR.CTL, otherwise all files inside your BBS areas will
eventually be deleted. Most obvious usage for this option is
to include file-masks that CAN be deleted like packages from
offline readers, DOWNLOAx.xxx (from DISP MTS.EXE) and so on.
[mask] must be a valid file-mask (wildcards are allowed) of
a file that can be deleted after a successful
download.
Example : DelAfterDL DOWNLOA*.*
─────────────────────────────────────────────────────────────
Means : All files which match the file-mask DOWNLOA*.* are deleted
after one successful download.
─────────────────────────────────────────────────────────────
┌─────────────────────────────────────────────────────────────────────┐
│ AlienArchive [extension] │
└─────────────────────────────────────────────────────────────────────┘
Usage : FileDoor has a build-in knowledge of most normal archivers.
Some other files could also be archives but of the type that
FileDoor does not know internally. BMP/TIF/PCX and such
could be such files.
You can add up to 10 AlienArchive options. [Extension] is
the extension of these special files. FileDoor will first
look if the file is a normal archive and then take a look at
the AlienArchive options to see if you have included this
file. Please add at least 'AlienArchive GIF' (if you want
the to be counted as archives) because 2.01a contained
coding to see a GIF as an archive but 2.02 does not contain
this coding anymore.
Example : AlienArchive PCX
─────────────────────────────────────────────────────────────
Means : PCX files (*.PCX) are marked as archives.
─────────────────────────────────────────────────────────────
┌─────────────────────────────────────────────────────────────────────┐
│ Ratio [sec] [ratio] [K|F] [threshold] │
└─────────────────────────────────────────────────────────────────────┘
Usage : You can have FileDoor check the current users file ratios
and allow him depending on these figures to download or not
to let him download files from your system. Both KiloBytes
and number of files are allowed. The first option is the
user's security level, the second the ration he must
maintain, the third one decides wether the amount of kB's or
the number of downloaded files is tested. The fourth option
is the free threshold for ratios. FileDoor will allow
downloads until the number set in the fourth parameter. Only
when this number is reached, Filedoor will start counting
the downloads, with the files downloaded during the free
threshold counted in. Up to 100 ratios are allowed, but only
one per security level.
Example : Ratio 100 10 F 20
─────────────────────────────────────────────────────────────
Means : Security level 100 must maintain a 1:10 file-number ratio but
until the 20th file, the downloads are not checked against
the ratio !
─────────────────────────────────────────────────────────────
┌─────────────────────────────────────────────────────────────────────┐
│ PrivateUploads │
└─────────────────────────────────────────────────────────────────────┘
Usage : If set the private uploads (to the Sysop) are allowed. The
description is placed in a separate file, PFILES.BBS in the
upload directory. The user has to start the filedescription
with a '/' to make an upload private.
Example : PrivateUploads
─────────────────────────────────────────────────────────────
Means : See description
─────────────────────────────────────────────────────────────
┌─────────────────────────────────────────────────────────────────────┐
│ TouchUploads │
└─────────────────────────────────────────────────────────────────────┘
Usage : If set all uploads will get the date/time stamp of your
system and not the original date/time. This way all uploads
will be displayed as *NEW* files.
Example : TouchUploads
─────────────────────────────────────────────────────────────
Means : See description
─────────────────────────────────────────────────────────────
┌─────────────────────────────────────────────────────────────────────┐
│ ULMultiply [sec] [multbyte] [multtime] │
└─────────────────────────────────────────────────────────────────────┘
Usage : This is a very powerful option. With the ULMultiply option
you can govern the credit that you will give to your users
when they do uploads. This can even be different for the
different security levels you use.
[sec] This parameter must be set to the security level
for which the following credits will rule. Only
users with this (exact) security level will get
the supplied credit when uploading files;
[multbyte] This must be a percentage ! This percentage will
be the credit for users with security level [sec]
that do uploads. The percentage is used to credit
the number of uploaded BYTES ! Values less than
100 will mean a reduction and values above 100
will mean a credit;
[multtime] This must be a percentage ! This percentage will
be the credit for users with security level [sec]
that do uploads. The percentage is used to credit
the number of minutes the user needed for the
upload (so it is a time-credit). Values above 100
will mean a credit, values under 100 will mean a
reduction;
Normally the user will be credited for the time the upload
but this can be set to a higher value !
Example : ULMultiply 100 200 400
─────────────────────────────────────────────────────────────
Means : All users with security level 100 will get 200% of the
uploaded bytes (so uploaded 1000 bytes will result in
counting this as 2000 bytes) and will also get 400% of the
upload-time (needed 2 minutes, will result in 8 minutes
credit, so 8 minutes minus the original 2 minutes upload
will come to a credit of 6 minutes).
─────────────────────────────────────────────────────────────
┌─────────────────────────────────────────────────────────────────────┐
│ AskAnother │
└─────────────────────────────────────────────────────────────────────┘
Usage : If set, FileDoor will ask the user if he wants to perform
another file-transfer after completing a transfer.
Example : AskAnother
─────────────────────────────────────────────────────────────
Means : See description
─────────────────────────────────────────────────────────────
┌─────────────────────────────────────────────────────────────────────┐
│ TimeOut [amount] {HANG} │
└─────────────────────────────────────────────────────────────────────┘
Usage : This will set the number seconds before FileDoor will
timeout a user for inactivity. This way you will prevent a
user to enter FileDoor and use all his BBS access time doing
nothing. After timing out a user he will be warned and
eventually be returned to the BBS.
[amount] must be the number of seconds that must pass before
FileDoor will time-out the user. There will be
warnings before the actual time-amount;
{HANG} If you supply HANG, FileDoor will drop the DTR
(thus the carrier) at once. Without HANG, FileDoor
will return to the BBS first. The BBS has then to
decide if the user must be disconnected (will take
extra time);
Example : TimeOut 180 HANG
─────────────────────────────────────────────────────────────
Means : After 3 minutes, FileDoor will disconnect the user if there
wasn't any activity during that period.
─────────────────────────────────────────────────────────────
┌─────────────────────────────────────────────────────────────────────┐
│ NoLastChance │
└─────────────────────────────────────────────────────────────────────┘
Usage : If the user choses to disconnect immediately after a
transfer FileDoor will ask the user to press any key to
terminate the hang-up process. NoLastChance will disable
this feature.
Example : NoLastChance
─────────────────────────────────────────────────────────────
Means : See description
─────────────────────────────────────────────────────────────
┌─────────────────────────────────────────────────────────────────────┐
│ NoLogOff │
└─────────────────────────────────────────────────────────────────────┘
Usage : When you have tuned FileDoor in a way that the user can
restart FileDoor from within FileDoor (AskAnother option) it
could be handy to disallow a logoff from within FileDoor
(which is normally available when the AskAnother option is
set). You can disallow any logoff inside FileDoor when you
supply the optional NoLogOff option.
Example : NoLogOff
─────────────────────────────────────────────────────────────
Means : See description
─────────────────────────────────────────────────────────────
┌─────────────────────────────────────────────────────────────────────┐
│ MinSpace [amount] │
└─────────────────────────────────────────────────────────────────────┘
Usage : With this option you will be able to set the minimum of
disk-space that must be free for allowing uploads to your
system.
[amount] must be set in number of KB's of space that must
left to allow any upload.
Bi-directional protocols (Bimodem/BiDSZ) will only case a
display of the minimum space but will allow uploads anyhow.
If the option is left out, no compare is made but the
available space will be displayed only.
Example : MinSpace 1000
─────────────────────────────────────────────────────────────
Means : At least 1000Kb must be available on the upload-drive to
allow any uploads.
─────────────────────────────────────────────────────────────
┌─────────────────────────────────────────────────────────────────────┐
│ NoEMS │
└─────────────────────────────────────────────────────────────────────┘
Usage : When this option is available, FileDoor is forced to ignore
EMS for swapping space (if needed). If there is still XMS or
Extended Memory, FileDoor will use this type of memory. If
neither of these two resources is available, FileDoor is
forced to use disk-space. When NoXMS is also present in the
FileDoor.CFG, disk-space is always used for swapping;
Example : NoEms
─────────────────────────────────────────────────────────────
Means : See description
─────────────────────────────────────────────────────────────
┌─────────────────────────────────────────────────────────────────────┐
│ NoXMS │
└─────────────────────────────────────────────────────────────────────┘
Usage : When this option is available, FileDoor is forced to ignore
XMS and Extended Memory for swapping space (if needed). If
there is still EMS, FileDoor will use this type of memory.
If EMS is not available, FileDoor is forced to use
disk-space. When NoEMS is also present in the FileDoor.CFG,
disk-space is always used for swapping;
Example : NoXMS
─────────────────────────────────────────────────────────────
Means : See description
─────────────────────────────────────────────────────────────
┌─────────────────────────────────────────────────────────────────────┐
│ DownloadHours [period] {baudrate} │
│ UploadHours [period] {baudrate} │
└─────────────────────────────────────────────────────────────────────┘
Usage : These options can be used to set periods in which downloads
and uploads are possible ( also for specific baud rates).
You can use a number of these options (unlimited) to set
different periods. If you don't use either one of these
options, the whole 24 hour is counted as a period in which
there can be downloads and uploads.
[period] This must be a block of two times in the format
hhmm-hhmm (where hh is the hour and mm the
minute) separated with a dash. A period must
NEVER extend midnight;
{baudrate} This can be set at the LOWEST baudrate for which
this period will govern. If no {baudrate} is
given, 0 is assumed (all connect will be 0 baud
or higher so they can all enter the down/upload).
An extended example. You want to have the upload-hours
between 18:00 and 02:00 and the download-hours run from
16:00 until 18:00 for all users, from 18:00 to 21:00 for all
users with 2400 baud or higher and from 21:00 to 02:00 for
all users with a 9600 baud connect (or higher). This will
need the following options:
UploadHours 1800-2359
UploadHours 0000-0159
DownloadHours 1600-1759
DownloadHours 1800-2059 2400
DownloadHours 2100-2359 9600
DownloadHours 0000-0159 9600
As you can see, all periods needed are covered. The only
thing you must watch is not to run a period inside one
option over midnight.
If a period is closed for download (or upload), FileDoor
will display DNLDHRS.Axx or UPLDHRS.Axx (when available).
When the connect is too slow for the period, TOOSLOWD.Axx or
TOOSLOWU.Axx are displayed (when present in the directory
pointed to by the FileDoorDir option).
Example : DownloadHours 0900-1200 9600
─────────────────────────────────────────────────────────────
Means : Open for downloads between 0900-1200 and only for 9600 or
higher baudrates. Uploads can be done always. Your users
will 'love' this setting.
─────────────────────────────────────────────────────────────
┌─────────────────────────────────────────────────────────────────────┐
│ CheckDupes {sec} │
└─────────────────────────────────────────────────────────────────────┘
Usage : If set, FileDoor will perform a dupe-check (internally) on
the uploaded files. All dupes are removed before they are
counted. TRY.ZIP is considered a dupe with TRY.ARC but
TRY.ARJ is NOT considered a dupe with TRY.ALL. Archive
extensions that will be tested are ARC, PAK, PKA, LZH, LZS,
ZIP, ZOO, DWC, MD, HYP, ARJ, SDN. If this check is to raw
for your taste, you can insert an exit (hook) in one of the
ExitAfterUpload options. The called file will then be
responsible to remove (and report) the duplicated files.
{sec} is an optional security level. If it is set, all users
with that level (or higher) WON'T get their files
checked for duplicates. This comes in handy for your
CoSysop or other users who are allowed to upload
duplicate files.
Example : CheckDupes 10000
─────────────────────────────────────────────────────────────
Means : All users up to security-level 9999 will have their uploads
checked for duplicates.
─────────────────────────────────────────────────────────────
┌─────────────────────────────────────────────────────────────────────┐
│ TagFileMacro [dir] │
└─────────────────────────────────────────────────────────────────────┘
Usage : This version of FileDoor allows third party utilities to
supply a tag file to FileDoor. This way programmers have a
way to pass on a list of selected files to FileDoor.
FileDoor will detect the tag files from RFW (c) and MTS (c)
automatically. The structure of this FileDoor/DISP
compatible tag-file is present in the release-archive.
[dir] must point to the common location where the tag-files
are placed. MTS and RFW (DISP products) have options
to point to that directory. The file-name will be
created by FileDoor itself.
Please read the chapter on tagging for more details on the
FileDoor/DISP-compatible tag-file.
Example : TagFileMacro D:\BBS\RA
─────────────────────────────────────────────────────────────
Means : Tag-files will reside in D:\BBS\RA and will be loaded from
that location (if available).
─────────────────────────────────────────────────────────────
┌─────────────────────────────────────────────────────────────────────┐
│ NewFileMacro [seclevel] {auto_display} {ask_areas} │
└─────────────────────────────────────────────────────────────────────┘
Usage : If this option is enabled FileDoor will allow your users
with a security level of [seclevel] (and higher) to easily
detect, select and download NEW files since their last logon
to your system.
[seclevel] must be the security-level from which on
users can use /NEW while inside FileDoor
<tm>;
{auto_display} If set to 'Y' (no quotes), FileDoor will show
the tag at startup. In this case, users are
reminded at once that they can use /NEW
otherwise they should obtain their knowledge
from the help-screen. If you don't want to
display the tag at once but you need the next
parameter, you must code a 'N' for this
parameter;
{ask_areas} If set to 'Y' (no quotes and the previous
parameter must be set), users are asked for
EACH eligible area if FileDoor should search
that area for new files;
Example : NewFileMacro 100 N Y
─────────────────────────────────────────────────────────────
Means : Users with security level 100 (and higher) will have the
option to use the /NEW macro. This will be displayed at the
startup of FileDoor.
─────────────────────────────────────────────────────────────
┌─────────────────────────────────────────────────────────────────────┐
│ NoShowInternalMacros │
└─────────────────────────────────────────────────────────────────────┘
Usage : Normally FileDoor will show the user all available macros at
startup. These include the external (UserMacro), pseudo
external (NewFileMacro) and internal (/USER, /UDEL, /TAG and
so on) macros.
If you set this option, FileDoor will not show the internal
macro's at startup. The user must access the help-screen to
show the available (internal) macros.
With this option set and the possibility to select if you
want to show external and pseudo-external macro's you can
decide if you want to show all, some or none of the macro's
at startup.
Example : NoShowInternalMacros
─────────────────────────────────────────────────────────────
Means : See description
─────────────────────────────────────────────────────────────
┌─────────────────────────────────────────────────────────────────────┐
│ UserMacro [tag] [auto] [desc] [mask] {sec} │
└─────────────────────────────────────────────────────────────────────┘
Usage : This option allows a user to use external macros. An
external macro is a simple name for a certain file. Lets say
that your allfiles-file is called AF512100.ZIP, you can now
create a macro (also called tag) with the name ALLFILE that
points to this file. The only thing the user has to do, is
to supply /ALLFILE on the file-selection menu. FileDoor will
start a search for AF512100.ZIP and the user can
(optionally) select the file for download.
[tag] is the name you want to use for the macro. Up to 8
digits are allowed;
[auto] can be set to either 'Y' or 'N' (no quotes). If set
to 'Y', FileDoor will display this macro (tag) at
startup, otherwise the user must obtain the name from
the help-screen;
[desc] is a short (32 bytes or less) description of the
macro. Any spaces in the description must be codes as
underscores. FileDoor will replace the underscores
with spaces when displaying the description;
[mask] points to the file (or filemask) that is meant to be
downloaded. When you use a simple filename or a
filemask (?, *), FileDoor will start a search party
for the file(s). When you include a drive, directory
and filename (no wildcards), you can even point to
files outside the normal BBS areas.
{sec} This optional parameter can be set to the lowest
security-level that is allowed to use this macro.
Example : UserMacro MTA Y The_newest_MTA_Package MTA_V???.??? 20
─────────────────────────────────────────────────────────────
Means : The user with security level 20 or higher can use /MTA to
obtain the latest MTA-package. The macro will be displayed
at startup.
─────────────────────────────────────────────────────────────
┌─────────────────────────────────────────────────────────────────────┐
│ SysopPassword [password] [sec] │
└─────────────────────────────────────────────────────────────────────┘
Usage : If a users enters // in the file-selection menu she/he will
be presented with the new questions: 'Enter password' and
'Give full path and filename of the wanted file'. This way
the cosysop or every other user you give knowledge of the
password and has the right security, will be able to
download from every directory on your system if hers/his
sec.level is the same or higher than a given level.
[password] can be up to 20 characters without spaces.
The case is not important.
[sec] must be set to the security level at which you
allow the usage of the // macro;
The user must enter a filename (full) and (optional,
when the file is not in the current directory) a full path
to the file (including drive when the directory is
not on the current drive). Only one file at the time can
be selected (no wildcards allowed) but // can be used
multiple times before the actual download has to start.
There is no other check whatsoever to the selected file
and your complete system is open for download.
Example : SysopPassword MySecretPwd 10000
─────────────────────────────────────────────────────────────
Means : Users who know the password MySecretPwd can access files
they can normally not obtain (USERS.BBS, be warned !!) if
they have security-level 10000 or higher !
─────────────────────────────────────────────────────────────
┌─────────────────────────────────────────────────────────────────────┐
│ PasswordProtect [mask] [password] │
└─────────────────────────────────────────────────────────────────────┘
Usage : Up to 100 PasswordProtect options can be included. You can
use this option to protect files with passwords. When a user
selects a file with a password, she/he has 3 chances to
supply the password. After the 3th try the user is returned
to the file-selection.
[mask] must be a filename or filemask (with wildcards)
that you want to protect;
[password] is the password that is assigned to [mask]. It
can be up to 8 characters and case will always be
converted to uppercase;
Example : PasswordProtect QEM*.* DISPAWARE
─────────────────────────────────────────────────────────────
Means : If a user wants to download a file that matches mask QEM*.*,
a password (DISPAWARE) must be given !
─────────────────────────────────────────────────────────────
┌─────────────────────────────────────────────────────────────────────┐
│ LockPassword [password] {STARTUP} │
└─────────────────────────────────────────────────────────────────────┘
Usage : You can lock FileDoor from the local side. This comes in
handy when you don't want to allow anyone (from Kat to
Child) to press any key inside FileDoor when you are not
looking. ALT-L will do the trick and ALT-X will put FileDoor
back in 'accepting-mode'. ALT-L and ALT-X will only work
when you supply a password with this option.
[password] is a password that is needed after pressing the
ALT-X key;
{STARTUP} If you code STARTUP (optional), FileDoor will be
in locked mode at startup;
Example: LockPassword NoKats STARTUP
─────────────────────────────────────────────────────────────
Means : If FileDoor starts, the keyboard is locked and the Sysop must
supply ALT-U with password NoKats to unlock the keyboard.
─────────────────────────────────────────────────────────────
┌─────────────────────────────────────────────────────────────────────┐
│ ExitAfterSelect [program] [options] │
└─────────────────────────────────────────────────────────────────────┘
Usage : This exit is called after EVERY 'Y' on a file-select with
download. If the called program returns errorlevel 0, the
file is allowed, if the errorlevel is 1 or higher, the
selection is denied even after FileDoor has allowed it
before.
[program] must point to the program you want to call and must
include drive, directory and full program name;
[options] must be the command-line for the specified
program. You can include multiple macros
(described later) to be replaced by FileDoor.
Example : ExitAfterSelect C:\UTILS\CALCUSER.EXE $C $B $U
─────────────────────────────────────────────────────────────
Means : After each selection (for download), CALCUSER.EXE is called.
─────────────────────────────────────────────────────────────
┌─────────────────────────────────────────────────────────────────────┐
│ ExitAfterDownload Drive:\Path\Filename.Ext [options] │
└─────────────────────────────────────────────────────────────────────┘
Usage : This exit is called after the download (successful or not)
and for EVERY file that was selected. In combination with
the ExitAfterSelect you can decide to do something to the
selected files (for example, add a file or comment with your
compress-program) in the ExitAfterSelect and reverse this
action on the ExitAfterDownload option to reset the file to
its original state. The problem of file sharing is up to the
program that is called in the exit.
In a later version, special options will be available to add
files and/or comments to archives before the transmission
and remove them afterwards but until then this could be
something for you !
[options] must be the command-line for the specified
program. You can include multiple macros (described later)
to be replaced by FileDoor.
Example : ExitAfterDownload C:\UTILS\CALCUSER.EXE $C $B $U
─────────────────────────────────────────────────────────────
Means : After the actual download, CALCUSER.EXE is called to perform
'its thing'.
─────────────────────────────────────────────────────────────
┌─────────────────────────────────────────────────────────────────────┐
│ ExitAfterUpload1 Drive:\Path\Filename.Ext [options] │
│ ExitAfterUpload2 Drive:\Path\Filename.Ext [options] │
│ ExitAfterUpload3 Drive:\Path\Filename.Ext [options] │
└─────────────────────────────────────────────────────────────────────┘
Usage : These exits are called after the upload. You can implement 3
of them. The exits are on their own. The fossil is closed by
FileDoor and parameters are passed to the called program.
[options] are the same as with the previous ExitAfterSelect
options. The command-line parameters for the
called program can also include macros that are
replaced by FileDoor.
The following macros are available to be implemented into
the command-line [options] of the called program:
- $C will be replaced with the Com-port number
- $B ,, ,, ,, ,, ,, Baud-rate
- $T ,, ,, ,, ,, ,, time-left to the user
- $S ,, ,, ,, ,, ,, allowed download-limit
- $Z ,, ,, ,, ,, ,, DSZLOG env. variable
- $U ,, ,, ,, ,, ,, upload-path
- $F ,, ,, ,, ,, ,, filename (ExitAfterSelect)
- $D ,, ,, ,, ,, ,, path to EXITINFO/DORINFO1
- $M ,, ,, ,, ,, ,, swap before exit is called
- $N if this option is present, the exit is ONLY called
when there are actual uploaded files;
A special note on the ExitAfterUploadx exits. A called
program can copy a file with the same name but with
extension F$D into the upload-directory. When this is the
case, a special routine will be triggered. FileDoor will
obtain the size of the original file from this file and will
NOT take the actual size. This routine is created so that
recompression (not recommended !!) can be done inside one of
the exits while FileDoor can still credit the user for the
actual number of bytes that were uploaded. One recompression
program that can do this job is MTA (version 15.xx) with
it's /STOSIZ option.
Example : ExitAfterUpload1 C:\UTILS\ZIPZOOM.EXE $C $B $U
─────────────────────────────────────────────────────────────
Means : After the actual upload, ZIPZOOM.EXE is called. Some macros
will be expanded.
─────────────────────────────────────────────────────────────
┌─────────────────────────────────────────────────────────────────────┐
│ ExitMasks [exit] [mask] {mask}..{mask} │
└─────────────────────────────────────────────────────────────────────┘
Usage : Normally the three ExitafterUpload1/2/3 exits will exit
after every upload. This can be a waste of time when the
exit will only test files with specific extensions like GIF.
For these cases you can include the ExitMasks option. If you
don't include the ExitMasks option(s), the exits will work
for all files.
[exit] must have the value U1, U2 or U3 to tell FileDoor is
this option is meant for the ExitAfterUpload1, 2 or 3
exit.
[mask] must be a valid file-mask (wildcards can be used).
You must supply at least one mask but you can supply
up to 5 masks on every ExitMasks option.
When, for a specific exit, you include the ExitMasks option
as well, the exit will ONLY be called when there is at least
one file uploaded that matches [mask] in the ExitMasks
option for that exit.
Example : ExitMasks U1 *.GIF *.JPG
─────────────────────────────────────────────────────────────
Means : The ExitAfterUpload1 exit will be called ONLY when there are
files uploaded which match *.GIF or *.JPG
─────────────────────────────────────────────────────────────
┌─────────────────────────────────────────────────────────────────────┐
│ AddFile [path] {only_bi} │
└─────────────────────────────────────────────────────────────────────┘
Usage : You can add up to 10 AddFile options. All files you supply
by means of AddFile options (each AddFile option must point
to a full drive, directory and filename) will be added to
the list of downloads (if there is still space to do so).
[path] must point to a file that you want to send along
with the selected files that will be downloaded.
{only_bi} is optional and, when used, must have a value of
'Y' (without the quotes). In this case, the file
pointed to by [path] will only be send when the
protocol is one of the bi-directional type.
If you love your users, you can think about sending a small
advertisement file (1K or less) instead of adding comments
(uncompressed) to all your files. Why bother the user with
the same advertisement over and over. Other sysop's that
download your files will use a program like MTA <tm> (DISP
program) to strip the comments right after receiving the
file.
Example : AddFile C:\USERS\ADVERTIS.ZIP
─────────────────────────────────────────────────────────────
Means : When the user starts the download (batch protocols only), the
file ADVERTIS.ZIP is added to the list of files to download.
─────────────────────────────────────────────────────────────
3.3.7 Filedoor's Protocol Definition
───────────────────────────────────────────────────────────────────────
This will be the toughest part of the Filedoor.Cfg. In this part you
will be shown how to install external protocols in FileDoor. An
example with almost every known external protocol has been included in
the package.
We strongly urge all filedoor users to share their knowledge and
experience with other and new protocols in FileDoor with the author.
This way we are able to update the examples and help users installing
these protocols in FileDoor. Please sent your information to the
author by Net or SnailMail or use the international echomail area
DISP.
Each protocol definition is made up by (at least) 2 or 3 options that
must be coded after each other. FileDoor will check if the
combinations you made are OK. For every protocol AND for every
direction of that protocol (upload and download) you want to include,
you must create a 'set' of these 2 or 3 command. The following order
is mandatory:
- PROTOCOL
This one comes first
- USAGE
This one is optional, but, if present, must follow PROTOCOL
- [prot-call]
This one is mandatory and must follow either PROTOCOL (in which case
you don't have a USAGE for this protocol/direction) or USAGE;
When FileDoor starts, it will take the eligible protocols, depending
upon the direction (triggered by -DD for download or -DU for upload),
the baudrate and the security and will store them in memory. The
number of protocols is only limited by the maximum number of lines
that can fit one screen (without a scroll) and should be enough to
give the user a wide selection of possible protocols.
Be very careful when you implement the protocols. Unexpected results
are almost impossible (FileDoor will give error messages) but it is
advised to run FileDoor locally a few times to test all the protocols.
┌─────────────────────────────────────────────────────────────────────┐
│ Protocol [effic] [letter] [direction] [maxfile] [MinBaud] [Text] │
└─────────────────────────────────────────────────────────────────────┘
This is the first line that will make up a complete protocol
description for a certain direction. The PROTOCOL option must be
completed with at least a [prot-call] option and (optionally) the
USAGE option.
If you want to implement a protocol (f.i. Zmodem) for both upload and
download, you need 2 sets of PROTOCOL/USAGE/[prot-call] options. One
for the 'direction' download and one for the 'direction' upload !
[effic] This must be the efficiency-rate of the protocol (it is a
percentage). When you don't have a clue about this rate,
you should take the supplied rates in the example file. In
short, if the efficiency is 100%, the protocol can manage
to send the bytes without overhead. Most protocols have
some overhead (ACK/NAK, CRC's and so on) and their rate
will not go over 95%. Some special protocols (and some
special connections, like MNP5/LAPM connections) are able
to raise the efficiency to 100% !
FileDoor uses the efficiency in 2 ways:
- When the user selects a file, FileDoor will calculate
the transfer-time, based on the baudrate and the
efficiency. A low efficiency will cause the calculation
to be lower, a high efficiency will cause it to be
higher. If you choose the efficiency too low, it will be
possible that some users select a file but will get a
deny message because FileDoor calculated that the
transfer would take to long. The reversed can happen
with an efficiency-rate that is too high. In this case,
the users would be able to select files without a deny,
while the actual transfer will take longer that the time
calculated by FileDoor;
- When using 'OTHER' types of protocols (see [prot-call])
FileDoor will assume a good transfer (download) when the
time needed for the transfer is the same as the time
calculated by FileDoor (there is a 10% margin). If the
rates are too low, FileDoor could assume that the
transfer was not OK, because the actual transfer took
less time than the time calculated by FileDoor;
In general, if you don't know the efficiency, use the
supplied examples or do some experiments yourself to see
what is best;
[letter] Each protocol is marked with a letter that can be used by
the user when the protocol-menu is presented. The letters
can be the same for different directions, so you can have
a 'Z' (for Zmodem) for download and a 'Z' (for Zmodem) for
upload, but you can't have the same letters for different
protocols for a given direction (so 'Z' for Zmodem
download and 'Z' for SZModem download is invalid).
FileDoor will check for duplicate letters and will
terminate. All letters from A-Z and all digits between 0-9
are allowed UNLESS you used one or two of these
letters/digits as the exit/help keys. The case of the
letter is not important;
[direction] You must supply either a 'D' for download or 'U' for the
upload. The 'B' that was used in previous versions of
FileDoor (2.xx) is now obsolete and should be replaced by
two new sets (one set with a 'D' and one set with 'U').
All PROTOCOL options with a 'D' are selected when FileDoor
is called with the -DD command-line parameter and all
PROTOCOL options with a 'U' are selected when FileDoor is
called with the -DU command-line parameter;
[Maxfile] Over here you must supply the maximum number of files that
can be transferred by this protocol in ONE session (from 1
to 255). Batch-protocols can have numbers above 1, old
protocols (OPUS types and Xmodem/YModem) must work with a
value of 1. FileDoor will stop the selection of files when
the number of already selected files has reached
[maxfile];
[Minbaud] This option is still present for historical reasons. It is
duplicated in the USAGE option but is also kept over here
so users of earlier versions of FileDoor can still use the
old PROTOCOL definitions. See USAGE for a description. If
there are values in both the PROTOCOL and USAGE options,
the one in the USAGE option will overrule the one in the
PROTOCOL option;
[Text] Over here you supply a text for the given protocol-letter.
You can supply up to 30 characters of text;
┌─────────────────────────────────────────────────────────────────────┐
│ Usage [minbaud] [sec] [arq] [win] [maxbaud] │
└─────────────────────────────────────────────────────────────────────┘
The USAGE option can be used to set some internal and security
options. USAGE is optional but when it is present, it must be put
between the PROTOCOL and [prot-call] options.
[Minbaud] This option can have a value from 0 to 999999. It is
matched with the baudrate of the user. If the users
baudrate is equal to or higher than [minbaud] the protocol
will be available for the user, otherwise it is not shown,
nor can it be selected;
[sec] This option can have a value from 0 to 65535. It is
matched with the security level of the user. If the users
security level is equal to or higher than [sec] the
protocol will be available for the user, otherwise it is
not shown, nor can it be selected;
[arq] This option can have a value of 'Y' or 'N'. You should use
a 'Y' (without the quotes) for those protocols that will
only work with modem-connects that have their own error
correction (a NMP-connect or ARQ-connect, mostly used with
highspeed modems). At present, FileDoor does NOTHING with
the value, but 3.10 will add the logic;
[win] FileDoor has 4 different spawn (shell) routines that can
be used when calling a protocol program. These are:
- Shell while swapping FileDoor from memory, full screen;
- Shell (without swap), full screen;
- Shell while swapping FileDoor from memory, windowed
screen;
- Shell (without swap), windowed screen;
The [win] parameter can be set to 'N' (full-screen shell)
or 'Y' (windowed-screen shell). If you select a windowed
shell, FileDoor will try to keep the last 4 lines of the
screen to itself (an extended status-bar), otherwise,
FileDoor will write a (unprotected) status-line on line 25
but it can be overwritten by the protocol. Some of the
protocols (Bimodem, Puma, Zyrion and such) need a full
screen, some of them can be installed to work in a smaller
window (GSZ) and some can be fully windowed (all line-type
protocols like DSZ). On some machines or with some cache
type of programs (older caches), the windowed screen won't
work, in which case you must use the normal full-screen.
If you don't use a USAGE parameter, the protocol will
always run in a full-screen;
[Maxbaud] This option can have a value from 0 to 999999. It is
matched with the baudrate of the user. If the users
baudrate is equal to or lower than [maxbaud] the protocol
will be available for the user, otherwise it is not shown,
nor can it be selected. If the parameter is left out,
FileDoor will assign a default of 9999999 so all baudrates
can use this protocol if also [Minbaud] is validated;
┌─────────────────────────────────────────────────────────────────────┐
│ [prot-call] [protocol] [options] │
└─────────────────────────────────────────────────────────────────────┘
This option MUST follow either after a PROTOCOL option or a USAGE
option. It is used to tell FileDoor about the protocol in question and
is the last of the 2 (3) options that make a full protocol definition.
There are several types of [prot-call] options, [prot-call] is only
used in this documentation to assign the whole group of options that
can be used. The only thing you must keep in mind is that there can
only be ONE of such options after the PROTOCOL or USAGE option !
[prot-call] The following values (options) can be used:
DSZ : This option tells FileDoor that this type of
protocol uses the DSZ rules. That means that
the protocol writes log-records in the log
that is assigned by the DSZLOG environment
variable and that these log-records follow
the same rules. Obvious, programs like DSZ
and GSZ (by Omen) are DSZ-types. SZModem can
also be setup as a DSZ-type of protocol.
FileDoor will obtain download-information
from the DSZ-alike log-file, so it is most
important that the protocol follows the
rules, otherwise the downloads could not be
counted or counted wrong !
BIDSZ : This option tells FileDoor that this type of
protocol uses the DSZ-alike syntax (so a
DSZ-log with that type of records) but can
work as a bi-directional protocol. At the
moment only HSLink can (must) be implemented
as such a protocol. The user will have the
option to supply BOTH uploads and downloads
(see BIMODEM type);
BIMODEM : This option tells FileDoor that the protocol
works as Bimodem <tm> and uses a BIMODEM.CFG
and a Bimodem-alike log-file. At this moment,
only Bimodem itself can be assigned as a
BIMODEM type of protocol (obvious). When this
type of protocol is used, FileDoor will ask
for both uploads AND downloads. If you use
-DD FileDoor will first ask for downloads, if
you use -DU, FileDoor will first ask for
uploads. In either case the user does not
need to enter a single file, because
Bimodem-alike protocols can use a special way
of download/upload (by means of an
Bimodem-internal communication file);
OPUS : This option tells FileDoor that this type of
protocol uses the OPUS 1.xx conventions. Some
of these protocols are MegaLink, OKermit and
CLink. All of them read a special file that
will be created by FileDoor and all of them
write a special file that will be re-read by
FileDoor to see if the transfers were ok;
ERRORLEVEL : This option tells FileDoor that this type of
protocol returns a non-zero errorlevel if the
transfer was not OK and that it is also a
protocol that can not be assigned as a
DSZ-type or OPUS-type of protocol. You should
always set the maximum number of files to be
transmitted in one run to 1 (never higher)
because when FileDoor gets a non-zero
errorlevel with more than one file, FileDoor
can not know which files were transmitted OK
and which didn't. In those cases ALL files
are marked as 'not-transmitted' and also not
counted;
OTHER : If none of the above options can be used, you
must a type of OTHER to the protocol. In this
case, FileDoor will calculate how long the
transfer will take (in seconds and minutes).
If it took that amount of time (or longer, or
up to 10% faster), FileDoor will mark the
transfer as ok, otherwise it will mark the
transfer as being not OK. As with ERRORLEVEL,
you should set the number of files to
transmit in one turn, to one (see above);
[protocol] On this location you must supply the filename of the
protocol program. You can select to use only the filename
(DSZ.COM) or a full path (C:\BBS\PROTOCOL\DSZ.COM). The
latter option is faster in execution (and more save) but
needs some extra work when you shift your protocol files
from one location to another one;
[options] Over here you place the options that are passed to the
protocol itself. You can include some macros that will be
replaced by FileDoor at run-time. These are:
$1 : Port number (1=COM1:, 2=COM2: etc)
$2 : Baudrate
$3 : Response file (for DSZ versions later then 880423 and
other protocols);
$4 : List of files to be received or sent
$5 : Number of minutes left
$6 : Number of kB left
$7 : Contents of DSZLOG environment variable
$8 : Upload Path
$M : Swap FileDoor from memory before executing the
protocol
$! : If added to the command-line, FileDoor will stop
the time internally and will restart the time
after the protocol has finished;
It is advised to use the $M as much as you can to preserve as much
memory as possible for the protocol !
Some general notes about the command-line:
- Calling the transfer-program with a complete path will load the
program faster than using the DOS path;
- $3 is used to generate a so-called DSZ-alike response file. Most DSZ
alike protocols can use this way of accessing the files which have to
be downloaded. When you use $3, FileDoor will generate a file with
on each line the full path to the file to be downloaded;
- $4 is used to generate a command-line, containing ALL files that have
to be downloaded. The command-line is limited (see below). If you
MUST use the $4, set the [maxfiles] value to the value of 1. Though
FileDoor will track the length of the parameter itself, the number of
files you can access in one turn (in this way) is VERY limited;
- The command-line in FILEDOOR.CFG is not limited in length, however
the expanded command-line as passed to DOS for execution may not
exceed 128 characters. This is DOS limitation;
- If you need a batch-file to start your protocol, you may do it as
follows: Other C:\COMMAND.COM /C MYBATCH.BAT [options]
Study the examples in the supplied FILEDOOR.CFG careful. There are
many users of FileDoor. These users can also help you with you quest
for the right options.
Example : keyword Download
| efficiency rate | maximum files
| | key to start | minimum baud Description
| | | | | | |
Protocol 92 G D 9 0 YModemG (DSZ)
Usage 300 1000 N Y 38400 -Maximum baudrate to be available
\ \ \ \-------Windowed operation
\ \ \---------No ARQ protocol
\ \------------Minimum security to be available
\----------------Minimum baudrate to be available
DSZ DSZ.COM Port $1 pB4096 restrict rb -k -g -$3 $M
| | \----------------------------------------\ |
| | command-line options ($3 = response file) |
| \-Driver |
\-Subtype Swap FileDoor to EMS/disk--/
─────────────────────────────────────────────────────────────
Means : Over here you see a fully explained example of an entry for
download (key G, 9 files max, 92% efficiency, called
YModemG) that is called by using DSZ.COM.
─────────────────────────────────────────────────────────────
3.4 FD_UPD and FILEDOOR.UPD
───────────────────────────────────────────────────────────────────────
For older QuickBBS versions it is impossible to reload information
from the EXITINFO.BBS. FileDoor will update EXITINFO.BBS with the new
credits so the BBS can reload this information at once but for the
older QuickBBS this is not possible.
In this case (QuickBBS) you must not only set SYSTEM QBBS but also
NoAutoUpdate in FILEDOOR.CFG. This means that FileDoor will start
creating a file called FILEDOOR.UPD in the supplied directory.
FILEDOOR.UPD is SHARE'ed like FILES.BBS. This can mean a little delay
at startup and termination BUT multiple FileDoor copies can access
FILEDOOR.UPD at the same time, so you CAN run multi-line without the
problems you had in previous versions.
When FileDOOR.UPD is created it will grow and grow. Every time
FileDoor will start it has to read FILEDOOR.UPD to update the users
credits from the USERS.BBS with the figures from FILEDOOR.UPD. For
this reason it is needed to empty this file once in a while (at least
every 24 hours).
In the package you will find a program FD_UPD.EXE. In your event you
must run FD_UPD with the FILEDOOR.UPD and the USERS.BBS (QBBS, SBBS or
RA) in the same directory. FD_UPD will update the figures from
FILEDOOR.UPD to USERS.BBS and at the end, FILEDOOR.UPD is deleted.
┌───────┬─────────────────────────────────────────────────────────────┐
│ 4 │ Runtime information │
└───────┴─────────────────────────────────────────────────────────────┘
4.1 Fast Modems
───────────────────────────────────────────────────────────────────────
If you use a modem running with a locked baudrate (HST/Telebit/V32
modems) you need to edit the command-line in the configuration file.
Two things need to be changed:
1. Replace all '$2' with the locked baudrate, 1.e. '19200' if you have
fixed the baudrate of your modem to 19200 baud.
2. Use the command-line options of the transfer program so that it
uses hardware handshake (CTS/RTS).
Transfer protocols that use the fossil-driver for all I/O don't need
any changes because the fossil driver will take care of the
handshaking and the locked baudrate.
4.2 Multi line operations
───────────────────────────────────────────────────────────────────────
FileDoor will work fine in a multi line setup. Previous versions could
trash files because there was a chance that the same file was updates
at the same time on different lines (FILES.BBS with FilesCount
option).
This version implements full sharing (when SHARE.EXE is loaded) for
those files that can be accessed from different lines at the same
time. Excluded are the log-files. You can let FileDoor write to the
BBS-log but there must be separate log-files for each line.
In some special cases, the user is asked to wait a few moments when
FileDoor is busy with updating FILES.BBS on two separate lines at the
same time.
You should (must) use different FILEDOOR.CFG files for each line you
run. A nice way to implement this, is to use the BBS's macro that is
replaced with the line-number, inside the call to FileDoor. You should
setup a menu type 7 (or 15) in the following way:
C:\UTILS\FILEDOOR.EXE -DD -CC:\UTILS\FILEDOOR.CF*N -N*N *M (RA)
In this way, a call on line 1 or 2 is expanded into:
C:\UTILS\FILEDOOR.EXE -DD -CC:\UTILS\FILEDOOR.CF1 -N1 *M (RA line 1)
C:\UTILS\FILEDOOR.EXE -DD -CC:\UTILS\FILEDOOR.CF2 -N2 *M (RA line 1)
There is a little flaw in Remote Access that makes it impossible to
use the *N more than once on the command-line. You can trick RA and
FileDoor by using *P for the first *N in the above command-line but
you can only do this when you your port (COM-port) and line are always
the same (so line 1 is COM1, line 2 is COM2 and so on). If this is not
the case, you can remove the -N*N option and add BBSLine 1 to
FILEDOOR.CF1 and BBSLine 2 to FILEDOOR.CF2.
From FileDoor version 3.01 (and up) it is also possible to make use of
a special tag inside the FILEDOOR.CFG. With this tag, it is now
possible to create one FILEDOOR.CFG that can be used on all lines;
All temporary directories and files are made line-specific. FileDoor
will use the line-number in all its temporary directories, swapfiles,
configuration-files and so on. There are no chances in cross-linking
any file.
WARNING: FileDoor uses the DSZLOG environment variable. You must set
this variable to a directory AND filename for EACH line and
the values MUST be different, so, for example, use:
SET DSZLOG=D:\BBS\RA\RA1\DSZ.LOG (on line 1)
SET DSZLOG=D:\BBS\RA\RA2\DSZ.LOG (on line 2)
If DSZLOG is not set, FileDoor will create one of its own.
If it is set, even then FileDoor will ALTER the value while
FileDoor is active unless a special option is set
4.3 Swapping
───────────────────────────────────────────────────────────────────────
When you run a BBS, you already know what swapping is. FileDoor can
swap itself from memory when the protocol is called. In this case you
must include $M into the command-line of the protocol(s).
FileDoor will first look for EMS, if not available than XMS is used,
if not available than extended memory is used, if not available than
DISK is used (the SwapPath option !). EMS and XMS can be skipped when
you set the NoEMS and/or NoXMS options in FILEDOOR.CFG !
4.4 FileDoor/DISP-compatible tag-file <tm>
───────────────────────────────────────────────────────────────────────
FileDoor can use a FileDoor/DISP-compatible tag-file <tm>. This is a
special structure, created by other doors like the DISP-programs MTS
and RFW. This tag-file will contain all the information for FileDoor
to access the filenames contained in this tag-file easy.
Other products can give an option to store information inside the
tag-file (filenames) and FileDoor can (later) access this information
In some way, the tag-file is a type of Clipboard where the user stores
filenames to remember and that can be recalled by the FileDoor
program.
FileDoor can use two kinds of tag-files. The first one is a normal
tag-file. The user MUST enter /TAG on the FileDoor selection question.
The second one is a so called AUTOLOAD tag-file. When the user selects
the download-menu, FileDoor will load the tag-file without having to
enter the /TAG on the selection line. The user is still able to select
or deny the tagged files. MTS and RFW will create autoload tagfiles.
When FileDoor recognizes a AUTOLOAD tag-file, it will display all
stored files for the user, so the user can add them to the download
list or skip them. Also FileDoor will remove the AUTOLOAD flag so the
next time FileDoor is started, there is still a tag-file (the same
when no new tag-file is created) but the user MUST access the file
with /TAG.
When FileDoor starts, it will look for BBSTAGFL.n (where n is the
line-number). If available, FileDoor will check if this tag-file
belongs to this user (with a name-compare). If this is not the case or
when the file is not compatible (IO-error, invalid), FileDoor will
remove it and /TAG is not possible.
4.5 File selection
───────────────────────────────────────────────────────────────────────
Reading this chapter can make the difference in FileDoor's speed
between a turtle and a road-runner (miep-miep).
You must think carefully how you will implement file selection for the
user. FileDoor offers a complete set of file selection methods but it
would be nice if you used the one that suits your environment (and
type of users).
FileDoor does everything from the point of the 'complete' set. See it
as a type of OOP way of working. The 'root' is the complete selection
and both you and the users can vary the behavior of this 'root'. Be
warned though that you alter the description of the file selection
help-file to the choice you have made. A generalized example of this
help-file is included in the release archive.
The 'root' is the base of all file selections that the user can make.
By default, FileDoor will use this 'root' method. A short description:
- The user is presented a line where she/he can enter 1 to the length
of the line file-masks. The different masks must be separated with
at least 1 space;
- After entering, FileDoor starts searching the area(s) for every
mask;
- When a match is found, FileDoor will ask the user (Y/N) if this is
the file that is requested. If 'Y', FileDoor will add it to the
list;
- In both cases, FileDoor will continue the search in the same (and
following, when AutoSearch is set) area(s) to search for this mask
until no match is left in either this or any other area(s);
The big benefit of this way of selecting files is, that it is very
friendly for the user, but advanced users will not like it at all.
Now there is an escape for this way of working and one that comes
close to the way that FileDoor 1.xx used. The user can enter /Q as the
last filemask and in this case ALL matches are taken without
questions, either until limits are exceeded or there are too many
files. The user will jump directly to the protocol (or the question to
start the protocol) and can go on from here.
Until now the user had only something to tell. The above method has
still one problem. When FileDoor finds a match it will still search
all eligible area's for more matches for the same file. This is needed
in those cases where name-like files can be available in two or more
different area's. In that case FileDoor MUST search because the user
could want the second (3th and so on) and not the first match. When
this is not the case, FileDoor can be implemented with another method.
There are two (related, but different) ways to do so:
- Add the ExactMatch in FileDoor.CFG;
- Now searching will as before but if the user enters a FULL filename
(without wildcards), FileDoor will take the first file with that
name that is found and no questions are asked for that file;
- The user can still make multiple selections by including a wildcard
in the name. Now FileDoor will go on searching for this file until
all available matches in all areas are processed;
There is a more radical method:
- Add the QuickMatch option in FileDoor.CFG;
- Now searching will be different. If a file matches a supplied mask,
the file is taken (no questions) and the mask is removed. Only other
masks that did not match until now, will processed until either all
files are found (e.g. all masks are removed) or all files are
processed (all areas have been processed when autosearch is on);
- The user is STILL able to overrule this method but in that case the
user must enter /S at the end of list of masks. In that case the
search will be the same as with the 'root' method;
There is one big advantage with ExactMatch or QuickMatch (never use
them both, QuickMatch will overrule ExactMatch but the program can
slowdown a bit). This advantage is speed. In the 'root' model,
FileDoor keeps on searching, even if all files are already selected,
for a possible other match. This is less with the ExactMatch method
(but the user must enter full names) and gone with the QuickMatch. The
number of informative lines with each option will be less than with
the 'root' method.
I suggest you only use QuickMatch on slow machines, big BBS's or those
BBS's that have their CD-rom as the last area(s) of the list. The
ExactMatch is somewhat in-between. FileDoor is at its most friendly
with both options set to off while there is still a quick method for
users who want is.
4.6 Selection with wildcards
───────────────────────────────────────────────────────────────────────
When the user enters filenames with wildcards, all available DOS
wildcards (these are '?' and '*') are possible. FileDoor (up from
release 3.01) extends the masks in two ways with both the same result:
- The user can use the DISP-compatible wildcard If a user enters =MTA
as a filemask, FileDoor will examine all files and those files that
have the word MTA inside will be matched. This is a 'shifted' match.
=TA.Z will match mTA.Zip, =V90 will match the files scanV90.ZIP and
cleanV90.zip and so on;
- The user can use the 4DOS <tm>-compatible wildcard If the user
enters *MTA*.* it will be expanded to =MTA and will do the same as
the DISP-compatible wildcard. With 4DOS-compatible wildcards you can
not search 'over the point' like with the previous method !
Both new wildcards will have one drawback. When FileDoor searches for
files with NORMAL wildcards, it uses DOS FindFirst/FindNext calls
which are very quick (in fact there are not that many protocol-drivers
that are as fast as FileDoor). When the user enters the special
wildcard, ALL files must be examined and this will take extra time.
4.7 Sysop-to-User files
───────────────────────────────────────────────────────────────────────
FileDoor implements a new method of putting special files aside for
SysOp's friend (or enemies). When the Sysop uses the program FileUSER
(it is more or less self explaining), she/he can put files aside for a
specific user PROVIDED THAT THE NAME ENTERED ON THE FILEUSER PROMPT IS
AN EXACT MATCH with the name the user uses on the BBS (there is no
check yet).
If you choose to do so, you can select if these files are to be free
or not and FILEUSER will put the files aside for the user (in a
special directory). In fact there are COPIES of these files in that
special directory. This is done, because FileDoor itself will remove
(delete) the files after the user downloaded those files. The syntax
for FILEUSER is:
FILEUSER {-C[filedoor.cfg]} {-N[line]}
-C and -N can be used just as with FileDoor itself (see chapter 3).
The -N is only used to select the right statements if you use the
line-tags in FILEDOOR.CFG.
FILEUSER itself is pretty much self-explaining. You will get a screen
where you can enter the filename. If you just hit the [ENTER] key, a
tag-list is presented and you can select one or more files (you must
tag them with the space-bar and after tagging you must hit the [ESC]
button). Also you will be asked the name of the user to send the files
to. FILEUSER will ask a description for the whole package (it will be
shown to the user when she/he enters FileDoor) and you can supply the
description of each of the files.
You can use FILEMAIN on a regular basis (inside the event) to clean up
files that have been set aside but were not collected. The syntax for
FILEMAIN is:
FILEMAIN R|U [days] {-C[filedoor.cfg]} {-N[line]}
At this moment, only the U can be used. If you use 'FILEMAIN U 10' and
run it in the daily event, FILEMAIN will cleanup all files (and the
temporary directories) that are 10 days or older. -C and -N have the
same meaning as with the normal FILEDOOR.EXE program. -N is used to
examine the line-tags inside FILEDOOR.CFG. If you don't use them, you
do not have to supply -N.
If you have set aside some files for someone and that user enters the
FileDoor program, she/he will get a message, telling that there are
files available for her/him. The user can now select the files, start
the download and return to FileDoor. After a successful download, the
files are removed until the last file is removed from the special
directory, in which case FileDoor itself will remove the other files
(the tag-file, the FILES.BBS) and the directory. If the user does not
want to download the files, she/he can use the /UDEL macro to delete
all private files at once. If the user WANTS to select the file, the
/USER macro can be used to do so !
In later versions of FileDoor, these options will be extended. The
interface is 'closed'. It is not hard to find out the way it works
but there is no guaranty that it will stay this way. Only the supplied
files (FILEMAIN and FILEUSER) will be at the same level as FILEDOOR.EXE
itself and can be used as such.
4.8 Local keyboard codes
───────────────────────────────────────────────────────────────────────
When FileDoor is active, you can use several ALT-key combinations for
different tasks. These are:
- ALT-J Jump to DOS The user gets a message that you have
shelled to DOS. Jump with a HOT-fossil;
- ALT-H Hangup This lowers the DTR of the modem and
the connection is zapped;
- ALT-G Hangup + message This lowers the DTR of the modem and
the connection is zapped. Before the
disconnect, the GOODBYE.Axx file is
shown to the user;
- ALT-X Lock keyboard This will lock the keyboard until ALT-U
is given (only works when LOCKPASSWORD
option is set in FILEDOOR.CFG);
- ALT-U Unlock Keyboard This will unlock the local keyboard
after you have supplied the correct
password;
- ALT-C Chat mode This will enter the external chat
program (only when ExternalChat is set
in FILEDOOR.CFG);
- ALT-B Back This will end FileDoor and will place
the user back in the BBS program;
Also you can use some function-keys to toggle the status-bar on the
local screen (if set).
4.9 FILES.CTL and BADFILES.CTL
───────────────────────────────────────────────────────────────────────
FileDoor can access two special files called FILES.CTL and
BADFILES.CTL. These files are common to most QuickBBS/RA/SBBS alike
BBS programs. The syntax for these two files can be found in the
documentation of your BBS program, but I will include some limited
information over here:
- BADFILES.CTL
This file contains lines with on every line a file-mask (wildcards
are allowed) of files that are unwanted for upload. The information
in this file is merged with the information from the UNWANTED
options in FILEDOOR.CFG. Duplicated masks will be dropped;
- FILES.CTL
This is a special macro-file with the following syntax:
[mask] {/UNWANTED} {/FREE} {/PWD=password}
QuickBBS <tm> and Remote Access <tm> don't use the /UNWANTED option
(they use the BADFILES.CTL) but SuperBBS <tm> does. From FileDoor's
point of view, it is perfectly safe to use the /UNWANTED switch in a
Remote Access environment also. [mask] is a filemask (with or
without directories and wildcards). If you use /UNWANTED, it will
mean that the file is unwanted for upload and will be merged with
the masks from BADFILES.CTL and the UNWANTED option in FILEDOOR.CFG.
Duplicated masks are not stored by FileDoor. The same goes for the
/FREE option. It means that a download of such a file is free for
the user. The masks with /FREE are merged with the FREEFILE option
in FILEDOOR.CFG. /PWD means that a file is protected with a password
and that this password must be supplied for a download. These files
are merged with those reported in the PASSWORDPROTECT option in
FILEDOOR.CFG.
You must know that FileDoor will store all information from FILES.CTL,
BADFILES.CTL and the FreeFile, Unwanted and PasswordProtect options in
dynamic memory. The more options you use, the more memory FileDoor
will need. You are advised to limit the number of options and files in
FILES.CTL/BADFILES.CTL as much as possible.
4.10 FileDoor and conversion exits (MTA.EXE and others)
───────────────────────────────────────────────────────────────────────
One of the strongest points for the upload-part of FileDoor is the
(possible) usage of exits. There are 3 exit-points defines (assigned
by the ExitAfterUpload1, ExitAfterUpload2 and ExitAfterUpload3
options) that are called one after each other. They are called AFTER
the transfer but BEFORE FileDoor starts checking the files. This means
that the programs, called inside one or more exits, can manipulate the
files BEFORE FileDoor can lay its hands on them.
After all exits are called, FileDoor will start looking for a number
of (so called) semaphore files that can be left behind by the programs
that were called in the exit(s). There are 3 semaphore files that the
FileDoor program will look for. They are (with their internal format):
nnnnnnnn.XS1 The nnnnnnnn is equal to a filename already inside the
temporary upload directory. If this file is present, it
contains 4 bytes (making a PASCAL LONGINT) with the
original length of the file after the transfer. This
semaphore is very useful when the user uploads A.ARC
(will result in a semaphore file A.XS1) which is then
converted inside the exit to A.ARJ (which will be much
smaller). If the semaphore is created, FileDoor will
count the ORIGINAL length of A.ARC and not the new
length of A.ARJ;
FILEDOOR.XS2 This semaphore is a text-file with records which are
made up of 12 bytes with the ORIGINAL filename after the
transfer AND 12 bytes with the new name after a
conversion. The file can contain a unlimited number of
24-byte records. If you run a conversion program that
converts A.ARC into A.ARJ but the user supplied the
comment to A.ARC BEFORE the transfer, FileDoor would not
detect the file after the transfer because the
conversion has renamed it to A.ARJ. In that case
FileDoor would ask a comment for A.ARJ from the user. If
the conversion renames the file, it should create an
entry in FILEDOOR.XS2 with the old and new name in one
24-byte record. FileDoor will read the semaphore file
and will know that A.ARC has been renamed to A.ARJ;
FILEDOOR.XS3 This semaphore is a text-file which contains sets of
records (9 records per set). The first record is the
name of the file, the second to 9th record each contain
1 to 45 bytes of text. If your conversion program is
able to extract a comments from the archives (most
obvious is the FILE_ID.DIZ file), it can then store
these comments in the FILEDOOR.XS3 file which will be
read by FileDoor. FileDoor can then use the comments as
defined by the SysOp (see InternalOverUser option);
One other 'trick' to mention is the removal of uploaded files. If your
exit can test for a virus and finds one inside an uploaded file, or
you run a GIF-test program that detects an invalid GIF, it can then
move that file to some trashcan (or even delete it). If the file is
gone from the temporary upload-directory, FileDoor won't count it at
all !
One program (obvious) that can make use of all these options is
MTA.EXE (by DISP). If you use the /STOSIZ, /STOCOM and /STONAM options
when you run MTA from within a FileDoor-exit, it will create the
mentioned semaphore files. Also (even when running in SIMULATE run) it
can detect an invalid archive or call a virus-test program. If illegal
files are found, it will move them to another place before FileDoor
will get its hands on it.
Soon there will be separate programs available that can run inside the
exits and that can do smaller (faster) jobs than MTA.EXE. If it is
just the FILE_ID.DIZ file you are after you should wait for such a
program, though MTA.EXE can do the job fine (along with a test for a
virus and more, even without conversion).
I have made it a policy to make this functions 'external'. This will
reduce the number of updates on FileDoor itself because it can still
run when a new type of comment-file hits the marked, new archivers
come by, archivers need new parameters and so on. Also the total
memory needed by FileDoor is reduced, so the 'bare-bone' user will not
have the overhead for these options !
┌───────┬─────────────────────────────────────────────────────────────┐
│ 5 │ Version information and credits │
└───────┴─────────────────────────────────────────────────────────────┘
5.1 The BETA-team
───────────────────────────────────────────────────────────────────────
Look into the file SUPPORT.XFD for a full list of all BETA testers and
support nodes.
5.2 Credits
───────────────────────────────────────────────────────────────────────
Thanks to the following people:
- Stig Jacobsen for developing FileDoor and making it possible to
create a State of the Art file-protocol interface.
- All registered users. You make it worthwhile to enhance FileDoor
with nice features;
- All users who did write a message and/or sent me a postcard;
- The 'true' believers that FileDoor is leading the marked for a price
that no one can match;
- The BETA-team;
5.3 Version history
───────────────────────────────────────────────────────────────────────
┌───────┬────────────────────────────┐
│ 2.01 │ Complete rewrite │
└───────┴────────────────────────────┘
■ The first release after the all rights and source codes have been
transferred from Stig Jacobsen to Rob van Hoeven. Can still contain
bugs (even DOS does) so......
┌───────┬────────────────────────────┐
│ 2.01a │ Bug release │
└───────┴────────────────────────────┘
■ Bimodem would fail (displaying help-screen) in some situations.
This is fixed;
■ All protocols would give various errors in local mode because most
of the time the COM0 (invalid port) was passed. Local testing will
now bring a window on-screen with the call that FileDoor will make
(program, location, options) when running remote;
■ GIF files were not counted as archives. This is (temporary) fixed
by including them as archive extension;
■ Backspace on remote side was not (always) destructive. This is
replaced with a 'backspace, space, backspace' combination;
■ Fixed some internal coding. Credit scoring for Bimodem upload in
download-menu was not counted. Fixed;
■ PFILES.BBS was a selectable file. This is now fixed. PFILES.BBS and
PFILES.BAK are now skipped;
■ Fixed problem with the upload-exits. They were not called when
Bimodem (possible uploads!) was selected in -DD or -DB menus;
■ Added a new option, HideFiles;
■ Added support for MTA 14.45 recompressing utility under FileDoor
ExitAfterUploadx options;
┌───────┬────────────────────────────┐
│ 2.02 │ 'Minor' and bug release │
└───────┴────────────────────────────┘
■ Fixed a problem where the download of Bimodem files was not counted
at all;
■ Aborted downloads in either DSZ, Other or OPUS flavour were always
counted. This could cause the following scenario. Download 40K,
abort after 20K, resume, abort at 30K, resume, abort at 39K,
resume, done. The user was counted for 20+30+39+40=129K and not
40K. This is fixed;
■ Errorlevel uploads could be counted as wrong when an exit was
called after the upload. This is fixed;
■ The problem with MinSpace is fixed at last (I hope). Both the
inter- nal coding AND the method are changed. I now use a faster
method and will also be able to cover more type of drives
(RAM-disk, LAN drives, SUBST-drives, ASSIGNed drives and such);
■ There is a flaw in some BBS programs that causes FileDoor to
display a very large number for the remaining download-credit. This
is the case when the downloaded KB's is set higher than the limit
(by the Sysop). This causes the reversed to happen. This is NOT a
problem of FileDoor but a problem of the BBS that passes the wrong
value to the door. A message is send to the author(s) of those
BBS's;
■ When there is no specific log-file present (all 3 types) and there
is nothing to add also, FileDoor would create a log-file with a 0
byte length. This is fixed;
■ The special upload/download log contained the name of the day and
not the month. This is fixed;
■ For SBBS users, the name of FILES.SBS is changed in FLSEARCH.CTL;
■ Clarified the search for FileDoor.CFG in the documentation;
■ Fixed a problem with the sharing of FILES.RA (and alike) files;
■ Fixed a problem with the sharing of HLP_*.* and MNU_*.* files;
■ The ASCII help-files could not be found. This is fixed;
■ Fixed various errors with errorlevel/other protocols and download;
■ Fixed the calls to various protocols (Bimodem to name one);
■ LHA archives with level-2 headers would not be detected. This is
fixed;
■ If -U is present on the call to FileDoor (and also -P, see later),
FileDoor will not check any UploadPath (PUploadPath) option in
FileDoor.Cfg for valid data;
■ Using // in the wrong way caused the previous selection (or trash)
to be displayed on the display. This is fixed;
■ After the selection of the protocol, FileDoor will now send a
clear-screen so there will be no trashed screen at the user side;
■ Added the NOEMS and NOXMS options;
■ Added PUploadPath (and -P) to move private uploads to a different
directory than the upload-directory (if wanted);
■ Did a complete facelist to the file-selection. Added /Q, /S to be
used by the user and ExactMatch and QuickMatch to be used by the
Sysop. See the new chapter for a discussion on the file- selection;
■ Changed the support for //. There will be a separate question for
the password and this password is protected on-screen with '*'.
■ Added AlienArchive option to point to special types of archives
that FileDoor has no knowledge of.
┌───────┬────────────────────────────┐
│ 2.03 │ 'Minor' and bug release │
└───────┴────────────────────────────┘
Be prepared for a long list of bugs, changes and features. It took
some time to create the new version so many user requests could be
implemented (others are implemented in 2.10, the next release). The
basic idea behind this release is to fix the real problems and to add
some small gigs. A small line in this list can make your day (or it
won't) !!!
■ Fixed the flag-support. It now works like the BBS. This should be a
relief;
■ Fixed the CTRL-Z problem that caused the FILES.BBS to trash and
make some editors go wild. Also the uploads will be logged in the
FILES.BBS ok (and no trash);
■ Fixed the hangup in FileDoor that was caused when a user used the
Bimodem <tm> protocol (registered or hacked) and added some files
to download. It could result in hanging FileDoor, hanging multi-
tasker, hanging machine or other strange things (I was trashing the
PC's memory);
■ Fixed the problem in multi-line operations with the 'SYSTEM FILE
(FILES.RA) NOT FOUND' error. I was sharing the file (thank you
folks, I received as many 'It is sharing-code 64' messages as I got
registrations) but forgot the sharing in one S.O.B. part of the
program (a removed line);
■ Fixed the problem where users were removed from FileDoor for no
reason with the CARRIER LOST or TIMEOUT/LOCKOUT message. This was
caused because of a weak filer in the input;
■ Fixed the problem where users could enter control-codes in the
input lines (same weak filer as above);
■ Fixed the problem where users would enter a file to upload twice
(or more) in the pre-selection, sending them once, and FileDoor
counting it twice (or more);
■ Fixed the problem with the RC=2 error when the protocols were in
the current directory when FileDoor got control;
■ The input-buffer was not cleared so when the user pressed 'Y' or
'N' to hard, they got more ('Y') or less ('N') files than they
wanted. Now the buffer is cleared before the next question;
■ With QuickMatch on, it was possible to enter *.* or ????????.???.
This is now filtered as a wrong file-mask;
■ Changed the user's command-line. The '[CR] to start download' will
only be presented when a file is selected (excluded is the infor-
mation file, see later) or when Bimodem is used;
■ Added the DupePath option to allow the movement (and not delete) of
duplicate files to a special directory;
■ Fixed a bug where FileDoor was counting IMb+ files as one tenth of
their actual size;
■ Fixed a bug where FileDoor was not seeing duplicate files when the
BBS was using ARJ for most files;
■ Reconfigured the logging (see documentation). It is important to
take some time to add the new features OTHERWISE LOGGING WILL RE-
SULT IN EMPTY LINES IN YOUR LOG !!!!!!!
■ Dupe files (upload) can now also be logged (see documentation);
■ Made the selection display somewhat smaller and added an option for
the user to read extended information about a file. This will
include the comment (up to 250 bytes, QFV/F/C +-commentline com-
patible), the name of the area, the size, the date and the time;
■ Enhanced the Color option with some colors that could not be
changed. Now they can;
■ Fixed 80% of the FOSSIL routines, causing less ticks to be snatched
from your other task(s) (under multitasking);
■ Added a Debug option;
■ Added a HelpExitKeys option;
■ Added a NotAvailText option;
■ Added the ExitAfterDownload option to call an exit after the down-
load;
■ Added information-file options. The user can now also download a
file with comments of the (previously) selected or downloaded files
EVEN with protocols that allow only 1 download at any time. If the
user stays in FileDoor, the info-file is kept and can be downloaded
UNLESS the user exits from FileDoor. Added the option DownloadInfo;
■ If the user selects <G>oodbye after transfer, FileDoor will now
display the GOODBYE.A?? screen;
■ If the user tries to download outside the normal hours, FileDoor
will display the DNLDHRS.A?? file;
■ If the HLP_???? file is not present, FileDoor will try to display
XFERHELP.A?? (if present);
■ Fixed a bug where FileDoor could leave the temporary directory
after a transfer. This is fixed;
■ Added some space to allow up to 255 protocols PER direction BUT
remember that the screen will scroll and every protocol will take
up to 172 bytes of memory;
■ Added ANSASC option to use different names for the menus and help-
files;
■ Added explicit support for SBBS 1.11 and up (FLSEARCH.BBS);
┌───────┬────────────────────────────┐
│ 3.01 │ Major release │
└───────┴────────────────────────────┘
I have split the 'what's new' information into 3 parts, the fixed bug,
any removed options and added (and enhanced) options.
Bug fixes:
───────────────────────────
■ Fixed a problem where filename in FILES.BBS in mixed case were not
updated and counted;
■ Fixed the major part of all swapping and shell routines. On some
machines they would hang;
■ The complete RATIO-system is revamped. It worked rather at random.
Some users could use it, others didn't. With the revamping all
critical errors are removed;
■ Fixed a problem with the %X macro in the logging-layout. When is
wasn't needed, it wasn't replaced by a null-string. Now it is;
■ FileDoor would not work ok with some combinations of the DISP
compatible +-comment-lines in FILES.BBS. This part has also been
rewritten;
■ When using Quickmatch, it was still possible to enter the file masks
*.* and/or ????????.???. This would cause all files to be selected
(up to the users limit). Though it is a user-error, the masks are
denied when QuickMatch is on;
■ FileDoor would show the N/A-text on locations where there actually
was a description. This is fixed;
■ Bimodem uploads for filename.ext would also cause a schedule for a
download for filename.ext. This would fail but the error in Bimodem
was not nice. Fixed;
■ All kind of strange things would happen if the user passed the
available time (uploads). In these cases the user was not able to
enter file-comments and some files were left in the temporary
directory. This if fixed;
■ Removed a number of invalid error-messages;
■ Removed a number of spelling errors;
■ Removed a (big) number of cosmetic errors;
■ Removed some beeps and bells that would drive the user crazy. The
warnings and information from FileDoor to the user is now much more
relaxed;
■ Trash could be entered in all log-files and FILES.BBS. Even a
truncate to 64K or less was possible. This has been fixed;
■ Some protocol calls would crash if there were no extra parameters
given. Also some protocols could not be found in these cases. These
routines are rewritten;
■ FileDoor would feel very happy when trash was on the command-line.
Now all command-line options are tested and the SysOp is mutilated
if there is a wrong command-line option;
■ Comments in the info-file would show the download-counters. These
are now removed (the counters, and only in the information-files);
■ You won't believe it but there have been a lot of reports from
Sysops who complained that user would enter 'Y' on the warning 'ARE
YOU THERE' (caused by a time-out from the user). This would cause
the next file to be selected. This has both been fixed. The message
is more clear AND the keyboard/modembuffer is flushed before the
user can go on;
■ Changed a lot of misleading and incorrect text into better verbs;
■ Upload descriptions could include spaces at the end, causing users
to enter 'Shit ' and FileDoor to validate the
text. Now FileDoor will truncate (trim) all spaces (front and end)
before counting the length of the comment (it is still possible to
enter 'Shit.......................');
■ After FileDoor did write inside a FILES.BBS, that FILES.BBS would
have a new date and time. This is now fixed, the original date, time
and attributes will be the same;
■ If a user entered a description before the actual upload while using
Bimodem AND a comment was also send thru Bimodem itself, the latter
would prefer. This has been reversed;
■ A problem with uploads at midnight is fixed;
■ Fixed a problem with the AlternateFILESpath. It always pointed to
the SYSTEM directory, whatever you supplied. Fixed;
■ Fixed a problem where only normal files (not READ-ONLY or other
attributes) could be selected. CD-ROM files are read-only, thus
fixed;
■ When using [V]iew on a non-archive file would report a strange
error. This has been fixed;
■ The pause (5 seconds) between the termination of a transfer and the
continuation of FIleDoor is not engaged when the carrier has
dropped;
■ Fixed a security leak. Though ..\USERS.BBS could be given when
selecting downloads, it was impossible to download the file. The
new ExternalView option made it possible to VIEW the file, so the
leak is closed;
Replaced features:
───────────────────────────
■ The -DB command-line parameter is removed. Please remove the menus
that use this parameter and convert the Bimodem entries ('B') to
either Upload ('U'), Download ('D') or both ('D' and 'U');
■ The HB and MB parameters for ANSASC are now obsolete or have a
different meaning (see ANSASC option);
■ The [direction] 'B' in the PROTOCOL option is now obsolete. Look
into the previous lines for conversion suggestions;
New/enhanced features:
───────────────────────────
■ Added the %B and %K macros for the log-layout, to be replaced by the
number of bytes or KBytes of the specific file;
■ Added the ^M macro for the log-layout, to be replaced by a CR+LF
sequence;
■ Added support for QuickBBS 2.75 (FILECFG.DAT);
■ Added ALT-key support for FileDoor (local side), see the chapter on
local keyboard interfaces;
■ Added option (LockPassword) to be able to lock the local keyboard;
■ The info-file (when selected at startup) is now added by FileDoor
even if the user did not supply /INFO. Only when there is still room
left for a fill to add (batch-protocols);
■ Added the SelMax option for small-housed (memory) computers;
■ Added the UserPath option for Sysop-to-user files. Also added the
FileUSER and FileMAIN programs to make it all work;
■ Just before the start of the protocol, the user will now see which
files are added by FileDoor (info-files, added by sysop);
■ Tags in the UserMacro options are now enhanced to 8 positions;
■ Files in the UserMacro options can now be outside the BBS-areas. In
this case you must supply a drive and directory along with the
filename;
■ Added a new log-file (for private uploads). Can be set with the new
PVTUploadLog option in FILEDOOR.CFG;
■ Added the USAGE option that works in combination with the PROTOCOL
option(s);
■ Added support for BADFILES.CTL and FILES.CTL. Use the FILEDOOR.CFG
options BADFILESName and FILESCTLName;
■ Expanded the TimeOut option with the HANG parameter;
■ FileDoor will now expand all filenames and directories when needed.
You can now supply paths without drives, relative directories and so
on (only for those options that explicitly need full path);
■ You can now return from the 'start protocol' menu to the 'select
file menu' when needed;
■ Added line-tags in FILEDOOR.CFG. You can now use ONE FILEDOOR.CFG
with all information for all the different BBS-lines;
■ FileDoor will now format and display all +-comment lines when you
ask [I]nfo for a specific file;
■ Added option (ExternalChat) to trigger an external chat-program with
ALT-C;
■ Added option (AddFile) to add files to the selected files (download)
from the Sysop side. This can be commercials and such;
■ Added option (UploadName) to add the name of the user in FILES.BBS
for every uploaded file. This has been implemented in several ways;
■ Added option (DelOldFiles) to delete uploaded files with a date that
is lower than the supplied limit (FileDoor will look INSIDE archive
files);
■ Support is added to update the USERON.BBS (under RA, see also the
UserOnPath option);
■ Support is added for LiveSystems USERON.EXE program (see also the
LiveSystemsPath option);
■ Added a status-bar on the local side (extended and in RA/QBBS
format). Also added the new StatusLine option in FILEDOOR.CFG;
■ Added a huge number of new ANS/ASC files (see included examples and
the description of the ANSASC option);
■ The can now be up to 5 DefaultExtension options;
■ Added routines to set the DSZLOG environment variable from within
FileDoor itself. Can be shut off with the new NoOwnDSZLog option;
■ Enhanced the ULMultiply option so FileDoor can now CREDIT upload
time (finally);
■ Added a windowed shell to the protocol. This will mean that the
status-bar can be protected (not updated) by FileDoor while the
protocol is running;
■ For some operations FileDoor would report 'Testing ....'. This has
been enhanced with a status-bar, so the user can see the progress.
These can be toggled with the NoDupeStat and NoFindStat options in
FILEDOOR.CFG;
■ Because FileDoor is unable to interpret the one-zillion of different
extended-ANSI codes (used by the BBS to be replaced by fancy things
as names, times and such), the GOODBYE screen could be displayed as
trash. You can now overrule the name of this screen to one that does
not contain these codes;
■ When only one protocol is available, FileDoor will not show the
protocol menu unless a special option is set in FILEDOOR.CFG (the
new option MenuIfOnlyOne);
■ Added support (finally) to make it possible to download a specific
file with FileDoor. Also the default protocol can be set in this
case, though I advise you to let the user make a choice. With this
option (-F and -X command-line parameters) you can now make one or
more specific menu entries to download the allfiles, the BBS-manual
and such. It is also possible to download a whole range of Sysop
pre-selected files when you include wildcards;
■ Added support to overrule the log-file name and location with a
command-line parameter (-L);
■ Added new option (ForceEdit) to force the user to check the
previously entered comment again after the upload;
■ Added a new macro to the protocol statement ($!) to stop the time
while the protocol is shelled;
■ If the user inputs filenames for uploads, they are also recorded in
the local BIMODEM.PTH file;
■ Added new option (BBSMAFormat, same format as BBSUPFORMAT). It is
used by FILEUSER.EXE and FILEMAIN.EXE (not by FILEDOOR.EXE). Only
the %R, %T and ^M macros will work with this option;
■ The NewFilesMacro has two new options. The first will deside if the
tag will be displayed at startup. The second will deside if the user
is able to search only certain areas for new-files (it will ask
questions for each area);
■ Added new option (NoShowInternalMacros) which can be used in a
combination with the UserMacro and NewFilesMacro to show all, some
or none of the available macros;
■ Added new option (Verify) which can be used to trigger the verify
files option in Bimodem;
■ CheckDupes is now enhanced. You can supply a security level at which
(or above) the user will not get a dupe-check on a file (CoSysops,
special users);
■ Added a special protocol type for HSLink-alike protocols. It is
called BiDSZ and can be used in combination with a PROTOCOL/USAGE
option;
■ A message (please wait) befor the call to the protocol is now
displayed;
■ The /NEW macro is enhanced and will now ask if the user wants to
search from the last time on or from a different date;
■ Duplicate Unwanted file-masks are now removed. Also when an unwanted
file in BADFILES.CTL or FILES.CTL diplicates, these are also removed
from the list (only one is shown);
■ Descriptions of the UserMacro option can now be 50 bytes long;
■ Added support for GIF, GIFLite and JPEG files;
■ After the protocol has finished, FileDoor will not check the time
anymore unless a new transfer is engaged. This will make it possible
to handle all actions in a normal way, even if there is no time
left;
■ Added new option (Delete0byteFiles) to remove any uploaded file of 0
bytes (optional);
■ Added a new macro ($N) to the ExitAfterUploadx options. If it is
present in the command-line, FileDoor will ONLY call the exit if
there really are uploaded files;
■ Added new parameters (RA11 and QNEW) to the SYSTEM option. RA11 must
be used for Remote Access 1.1x and QNEW for QuickBBS 2.75+;
■ Added new option (NoLogoff). Can be used in combination with
NoLastChance and AskAnother. If set, there is now way to logoff
(normally) from FileDoor;
■ Added new option (ExternalView) with support for an external view
program (MTS 7.59 and up);
■ Added new option (DelAfterDL) to delete certain files after the
actual download. Can be used for temporary files like the files from
offline mail-readers and the DOWNLOAx.xxx files from MTS;
■ Enhanced the [I]nfo option with various download times and speed for
different modem speeds and protocols;
■ Added new option (ExitMasks) to make it possible to call the exits
after the uploads ONLY when specific files were received;
■ Added support for external conversion programs that change the name
of the uploaded file(s) (like DISP's MTA.EXE);
■ Added support for external conversion programs to extract comments
from archives (like FILE_ID.DIZ) and to pass them to FileDoor (like
DISP's MTA.EXE);
■ Added new option (InternalOverUser) to overrule comments from the
user by comments from the archive;
■ Added support for DISP-compatible wildcards (=SCAN) and for
4DOS-compatible wildcards (*SCAN*.*);
■ Added new option (ExcludeFile) to exclude local and global files
(like FILES.BBS and others) from the file-selection;
■ Added an overlayed version of FileDoor which consumes 100K less of
conventional memory;
■ Enhanced the HideFiles option to allow users to select files that
are not in FILES.BBS if they supply the EXACT name;
■ Enhanced the DownloadHours option with an optional baudrate for the
lowest allowed connect;
■ Added new option (UploadHours). Is used as DownloadHours (also
possible with baudrates) but now for uploads;
■ Added a lot of new internal coding, changes in layouts, fixes for the
highest possible speeds and so on. It is well possible that I even
forgot to include some comments on new/changed features but I have
tried to include as much as possible;
■ Did a (almost) complete rewrite of the documentation;
■ Synchronized all ANS/ASC files and menus to the example FILEDOOR.CFG
and FILEDOOR.MUL files;
5.4 Copyright, Trademarks
───────────────────────────────────────────────────────────────────────
Bimodem is a trademakr of Eric Labs
4Dos is a trademark of J.P. Software / R.C. Conn and T. Rawson
DSZ and GSZ is a trademark of Omen Technology
Bimodem is a trademark of Eric Labs
HSLink is a trademark of Samuel H. Smith
FrontDoor is a trademark of J. Homrichhausen
SBBS is a trademark of Risto Virkkala and Aki Antman
MSDOS is a trademark of Microsoft(tm)
Windows is a trademark of Microsoft(tm)
QuickBBS is a trademark of Pegasus Software
Remote Access is a trademark of Continental Software
USERON is a trademark of LiveSystems
OS/2 is a trademark of International Business Machines (IBM)
PCDOS is a trademark of International Business Machines (IBM)
FileDoor is written in Turbo Pascal 6.0, with help of the Turbo
Debugger 2.5 and makes extensive use of Object Professional 1.14 and
OPCFI 12.01. Also included are some routines of TurboPower's ASYNCH
Professional 1.04, the SYSTEM.TPU is replaced with a registered
commercial release of SYS60a and also STRG61 (registered, commercial)
is included. Sources have been edited with Brief <tm>, documentation
has been edited with an old version of Multi Edit <tm>.
Turbo Pascal is a trademark of Borland International
Turbo Debugger is a trademark of Borland International
Object Professional is a trademark of TurboPower Inc.
ASynch Professional is a trademark of TurboPower Inc.
OPCFI is a trademark of Robert W. van Hoeven
FileDoor is a trademark of Robert W. van Hoeven
MTA, MTS and RFW is a trademark of Robert W. van Hoeven
SYS60a is a trademark of Eagle performance Software
STRG61 is a trademark of Eagle performance Software
Brief is a trademark of SolutionSystems
Multi Edit is a trademark of American Cybernetics
==================== END OF DOCUMENT ==================================